Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] XMLTV - tv_grab_zz_sdjson can't determine local timezone #236

Closed
1 task done
raccettura opened this issue Jul 6, 2023 · 4 comments
Closed
1 task done

[BUG] XMLTV - tv_grab_zz_sdjson can't determine local timezone #236

raccettura opened this issue Jul 6, 2023 · 4 comments

Comments

@raccettura
Copy link

raccettura commented Jul 6, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

2023-07-06 01:37:35.602 xmltv: /usr/bin/tv_grab_zz_sdjson: no output detected
2023-07-06 01:37:35.602 xmltv: /usr/bin/tv_grab_zz_sdjson: grab returned no data

Expected Behavior

Timezone should be set via:

export TZ=Timezone

Steps To Reproduce

  1. Setup XMLTV
  2. Try and run

Environment

- OS:
- How docker service was installed:

CPU architecture

x86-64

Docker creation

  tvheadend:
    image: linuxserver/tvheadend
    container_name: tvheadend
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Americas/New_York
#      - RUN_OPTS=<run options here> #optional
    volumes:
      - ./data/tvheadend/config:/config
      - ./data/tvheadend/.xmltv:/.xmltv
      - /mnt/video/:/recordings
    labels:
     - "autoheal=true"
    ports:
      - 9981:9981
      - 9982:9982
    network_mode: host
    devices:
      - /dev/dri:/dev/dri #optional
    restart: unless-stopped

Container logs

.
@github-actions
Copy link

github-actions bot commented Jul 6, 2023

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@aptalca aptalca added the invalid label Jul 6, 2023
@github-actions
Copy link

github-actions bot commented Jul 6, 2023

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.

@github-actions
Copy link

github-actions bot commented Aug 5, 2023

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Oct 4, 2023
Copy link

github-actions bot commented Nov 3, 2023

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

3 participants