A
AndSve
Guest
BackupManager in Vix 2.2.105 (and .100) seems to write illegal strings to /etc/enigma2/settings, in entry config.backupmanager.lastlog
My image is online updated from Vix2.2.1, no full reflash. Skin Vix HD.
Attached is the settings file as observed directly after BackupManager is run by manual start (settings_110726_2229_bkpmgr_saved)
Extract from Enigma2-log is attached (Enigma2-26-07-2011_22-22-54_partof.log)
Directly editing the settings file doesn't help as it is rewritten at next Enigma2-restart.
This restart fails, with repeated attempts as /usr/lib/enigma2/python/Components/config.py fails,
first Enigma2-log attached (Enigma2-27-07-2011_00-27-28.log).
Extract from syslog attached (Syslog 2011-07-27_partof.log)
Workaround:
Connect through ssh
enter 'telinit 4' to stop Enigma2 from being restarted
delete the multiline entry config.backupmanager.lastlog in /etc/enigma2/settings
enter 'telinit 3' to return to default runlevel with Enigma2 being restarted OK.
Enigma2-log from this start attached(Enigma2-27-07-2011_00-41-59_partof.log)
My image is online updated from Vix2.2.1, no full reflash. Skin Vix HD.
Attached is the settings file as observed directly after BackupManager is run by manual start (settings_110726_2229_bkpmgr_saved)
Extract from Enigma2-log is attached (Enigma2-26-07-2011_22-22-54_partof.log)
Directly editing the settings file doesn't help as it is rewritten at next Enigma2-restart.
This restart fails, with repeated attempts as /usr/lib/enigma2/python/Components/config.py fails,
first Enigma2-log attached (Enigma2-27-07-2011_00-27-28.log).
Extract from syslog attached (Syslog 2011-07-27_partof.log)
Workaround:
Connect through ssh
enter 'telinit 4' to stop Enigma2 from being restarted
delete the multiline entry config.backupmanager.lastlog in /etc/enigma2/settings
enter 'telinit 3' to return to default runlevel with Enigma2 being restarted OK.
Enigma2-log from this start attached(Enigma2-27-07-2011_00-41-59_partof.log)