Cant update timezone after restoring settings

[juntta]

Hi!

I had to restore my settings from backup yesterday and now I cannot set timezone right in Meteohub.

If I set my timezone right (Europe / Helsinki) in Settings page and press 'Save' it says

Code: Select all

symlink failed: File exists
Job scheduled for recalculation of weather data
Data Logging restarted

How can I fix this? Meteohub version 4.5i (build 46)

[Ettershaus]

The system want to make a Link (symlink) for the used time-zone to the default name of the time-zone, but there is still a file or link.

At my linux-system, not meteohub, i've a file names "/etc/timezone"
This file contains the value "Europe/Berlin"

[juntta]

Yes, I have that file too, /etc/timezone which has "Europe/Helsinki".

Debian shows timezone & time correctly and actually Meteohub shows time correctly too. But timezone is missing, both on 'System Info' & 'Settings' page.

Should I remove /etc/timezone file and reset settings in Meteohub or what?

[Ettershaus]

Intresting ;-)

On my Debian-System, this file has the following rights:

Code: Select all

-rw-r--r-- 1 root root 14 20. Okt 17:30 /etc/timezone

As i remenber, on the Meteohub system, they are the same.

Do you have the Timezone-Files in "/usr/share/zoneinfo".
You should have a filme named

Code: Select all

:~# ls -la /usr/share/zoneinfo/right/Europe/Helsinki
-rw-r--r-- 2 root root 2363 16. Okt 20:07 /usr/share/zoneinfo/right/Europe/Helsinki
:~# file /usr/share/zoneinfo/right/Europe/Helsinki
/usr/share/zoneinfo/right/Europe/Helsinki: timezone data
:~#

[juntta]

I have exactly same rights as you and same files you mentioned too... :S

[juntta]

No progress, I tried to "Reset Settings" from the "Maintenance" page and set timezone after that but still same error:

[juntta]

[Ettershaus]

I'll think, that's something for Boris.

It's strange, anyway.

[juntta]

Well, calling for Boris - are you listening...? :)

[andyF1]

Did anyone ever fins a resolution to this problem as I now have the same?
**Edit just found the answer! I have to upgrade to version 4.6m for the fix **