[SOLVED] Updater.sh does not finish, just hangs


#1

The updater hangs and will not continue. Rolling back to two days ago results in the same “error”. This is the latest output:

  • /etc/init.d/lighttpd restart
    Output from foris-diagnostics-plugin-l10n-de.postinst:
  • [ -n ]
  • /etc/init.d/lighttpd restart
    Output from luci-i18n-base-en.postinst:
    /usr/lib/opkg/info//luci-i18n-base-en.postinst: .: line 4: can’t open '/etc/uci-defaults/luci-i18n-base-en’
    Output from luci-i18n-commands-en.postinst:
    /usr/lib/opkg/info//luci-i18n-commands-en.postinst: .: line 4: can’t open '/etc/uci-defaults/luci-i18n-commands-en’
    Output from luci-i18n-base-de.postinst:
    /usr/lib/opkg/info//luci-i18n-base-de.postinst: .: line 4: can’t open '/etc/uci-defaults/luci-i18n-base-de’
    Output from luci-i18n-commands-de.postinst:
    /usr/lib/opkg/info//luci-i18n-commands-de.postinst: .: line 4: can’t open '/etc/uci-defaults/luci-i18n-commands-de’
    Output from foris-controller-openvpn-module.postinst:
  • [ -n ]
  • /etc/init.d/foris-controller restart
    Output from foris-openvpn-plugin.postinst:
  • [ -n ]
  • /etc/init.d/openvpn enable
  • /etc/init.d/lighttpd restart
    Output from foris-openvpn-plugin-l10n-de.postinst:
  • [ -n ]
  • /etc/init.d/lighttpd restart

Is there a more detailed log which shows what exactly is failing?

EDIT:
Rolled back again, removed l10n de, but updater hangs again:

Output from foris-wizard.postinst:

  • [ -n ]
  • /etc/init.d/lighttpd restart
    Output from foris-diagnostics-plugin.postinst:
  • [ -n ]
  • /etc/init.d/lighttpd restart
    Output from foris-controller-openvpn-module.postinst:
  • [ -n ]
  • /etc/init.d/foris-controller restart
    Output from foris-openvpn-plugin.postinst:
  • [ -n ]
  • /etc/init.d/openvpn enable
  • /etc/init.d/lighttpd restart

#2

Same happening to me. Contacted Turris support, no answers. If you check the main 3.10.1 thread there’s one other (@palo_m) with this issue as well. :expressionless:


#3

This worked for me: stop and disable ddns service, reboot, let the updater finish, then re-enable ddns.


#4

I can confirm that disabling the DDNS allows the updater to work.

Now my question, how did you find it out?


#5

It was mentioned in the 3.10.1 thread. Tried it, and it worked for me.


#6

Hello,
We have your email since Sunday as we don’t provide support 24/7 and I know that you wrote us, please be patient.

//EDIT: 13.6. 01:32 replied to you.


#7

My updater is hanging but ddns was already disabled. Any tipps on what might be blocking the updater from succeeding, or how to find out which process is blocking it?

The error message that appears sometimes is:

Updater selhal:

[string “backend”]:1194: [string “backend”]:1185: Failed to lock the lock file //var/lock/opkg.lock: Resource temporarily unavailable


#8

Same here. I already contacted support and they investigate it currently. I will report back in if it gets solved.