Questions: Update logging; Wizard problems

Hello,

I’m very pleased to have a Turris Omnia! I bought the 2GB version from in-ear.com and delivery was quick, from Prague to Minneapolis.

I have two questions, after looking for answers in the forum. Thanks in advance for any comments or corrections!

Before I get started, I’ll mention my network configuration. I plan to run the Omnia inside a firewall, and that’s where it is now. Perhaps I need to modify the iptables configuration on my outermost firewall (an Edgerouter Lite) for a happy Omnia.

Omnia performance is great, ~200Mbits/second wifi from my iPhone 7, both from the browser and from an app. This is a very nice router.

One. My first question is about updates, both automatic and manual. The automatic-update feature is a big reason why I bought this router. It isn’t clear to me, how I can tell what’s going on.

The update from the wizard never worked (that’s in my second question), so I used Foris to enable automatic updates.

Now I see log messages that make it clear that an automatic update did occur. (I’m a little concerned that there was a stack traceback, but I see on the forum that’s going to be fixed.) See below** for details of the automatic update, if they are useful.

So, after the automatic update, I tried a manual update:

> root@turris:~# /usr/bin/updater-unstuck.sh
> root@turris:~# /usr/bin/updater.sh
> WARN:Script revision-specific not found, but ignoring its absence as requested
> WARN:Script serial-specific not found, but ignoring its absence as requested
> WARN:Lock on //var/lock/opkg.lock released by garbage collector
> root@turris:~# 

Nothing was logged, so is it safe to say that there was nothing to update? In other words, if an update fails for some reason, will there be specific messages that say so?

Also, do I need to run /usr/bin/updater-unstuck.sh before I do a manual update? I see it in the crontab.

Two. My second question is about the setup wizard. I tried it five or six times, doing a factory reset after each try, and it never worked quite right.

The wizard has trouble with Internet connectivity until it says it will “disable forwarding” and then it works.

The wizard has trouble with NTP (so I synchronize time with my computer).

Every time I enable automatic updates in the wizard, it chugs along for ten minutes or so, displaying dozens of packages to update – and then it fails. Every time. Any suggestions?

Thank you! --Peter

**Details of updater log messages:

> 2017-05-20T13:29:58+02:00 info updater[9327]: src/pkgupdate/main.c:214 (main): Executing preupdate hooks...
> 2017-05-20T13:29:58+02:00 info updater[9327]: src/lib/util.c:141 (exec_dir_callback): Subprogram output: /etc/updater/hook_preupdate/05_schnapps.sh:
> 2017-05-20T13:29:58+02:00 info updater[9327]: src/lib/util.c:142 (exec_dir_callback): End of subprogram output
> 2017-05-20T13:29:58+02:00 err updater[9327]: src/lib/util.c:145 (exec_dir_callback): Subprogram output: /etc/updater/hook_preupdate/05_schnapps.sh:
> 2017-05-20T13:29:58+02:00 err updater[9327]: src/lib/util.c:146 (exec_dir_callback): End of subprogram output
> 2017-05-20T13:30:04+02:00 warning updater[9327]: requests.lua:335 (func): Script revision-specific not found, but ignoring its absence as requested
> 2017-05-20T13:30:06+02:00 warning updater[9327]: requests.lua:335 (func): Script serial-specific not found, but ignoring its absence as requested
> 2017-05-20T13:30:28+02:00 warning updater[9327]: backend.lua:1200 (flags_load): Couldn't load flags: cannot open /usr/share/updater/flags: No such file or directory
> 2017-05-20T13:30:35+02:00 info updater[9327]: updater.lua:95 (Globals): Queue install of psmisc/turris/22.16-2
> 2017-05-20T13:30:04+02:00 warning updater[9327]: requests.lua:335 (func): Script revision-specific not found, but ignoring its absence as requested
> 2017-05-20T13:30:06+02:00 warning updater[9327]: requests.lua:335 (func): Script serial-specific not found, but ignoring its absence as requested
> 2017-05-20T13:30:28+02:00 warning updater[9327]: backend.lua:1200 (flags_load): Couldn't load flags: cannot open /usr/share/updater/flags: No such file or directory
> 2017-05-20T13:30:35+02:00 info updater[9327]: updater.lua:95 (Globals): Queue install of psmisc/turris/22.16-2
[Here I omitted about 360 "Queue install" messages]
> 2017-05-20T13:35:17+02:00 info updater[9327]: updater.lua:95 (Globals): Queue install of luci-proto-relay/turris/git-17.009.29435-7d19852-1
> 2017-05-20T13:35:17+02:00 info updater[9327]: updater.lua:114 (Globals): Queue removal of luci-i18n-wshaper-en
[Here I omitted several "Queue removal" messages]
2017-05-20T13:35:17+02:00 info updater[9327]: updater.lua:114 (Globals): Queue removal of wshaper
> 2017-05-20T13:35:41+02:00 warning updater[9327]: backend.lua:886 (pkg_merge_files): Config file /etc/config/updater modified by the user. Backing up the new one into /etc/config/updater-opkg
[Here I omitted several "Backing up" messages]
> 2017-05-20T13:36:00+02:00 warning updater[9327]: backend.lua:886 (pkg_merge_files): Config file /etc/config/ucollect modified by the user. Backing up the new one into /etc/config/ucollect-opkg
> 2017-05-20T13:36:01+02:00 info cron[2780]: (*system*) RELOAD (/etc/cron.d/updater)

Hello,
Regarding automatic updates notification:
Log into Foris and go to the tab Maintenance and fill there your email address and set your importance as you want.

But if you don’t want fill your email you can see notification here on forum or you can check it on Reddit.

For manual update next time please do:

opkg update
updater.sh
(you dont need to do updater-unstuck.sh)

When updater fails for some reason there will be error message in Foris and also it will notify you by email, when you filled email in Foris

1 Like

You don’t have to run opkg update unless you are going to use opkg. It has no effect on updater it self. It no longer uses opkg.

Anyway. There is nothing wrong in log you posted. It’s just output from postinstall scripts and it’s fine.

On the matter of wizard problems. Our test detected some problems with your DNS server so it disabled forwarding to it. Most offten it is because your DNS server doesn’t validate DNSSEC. Running DNS with disabled forwarding is fine unless your ISP adds some internal domains as those won’t be resolved as they are not on authoritative DNS servers.
Failing updater is most probably caused just by timeout of wizard. If you would wait for ip address and renewed webside it would most probably just continued.
And time? You have stated that you are running TO behind firewall is it possible that you are just blocking access to all NTP servers?