**** BEGIN LOGGING AT Sun Apr 10 02:59:58 2016 Apr 10 04:40:03 build #210 of ixp4xx is complete: Failure [failed shell_7] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/210 Apr 10 04:49:36 build #211 of lantiq.xrx200 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq.xrx200/builds/211 Apr 10 09:50:52 build #205 of au1000 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/205 Apr 10 11:10:05 build #200 of mcs814x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/200 Apr 10 13:11:16 build #229 of x86.kvm_guest is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86.kvm_guest/builds/229 Apr 10 13:20:36 build #266 of lantiq is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/266 Apr 10 13:53:25 build #236 of ar71xx.nand is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx.nand/builds/236 Apr 10 14:36:05 build #216 of arm64 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/arm64/builds/216 Apr 10 14:41:35 build #199 of uml is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/199 Apr 10 14:48:36 build #197 of ath25 is complete: Failure [failed shell_7] Build details are at http://buildbot.openwrt.org:8010/builders/ath25/builds/197 Apr 10 15:03:40 build #192 of adm8668 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/adm8668/builds/192 Apr 10 15:08:21 build #193 of mvebu is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/193 Apr 10 15:12:32 build #196 of ar71xx.mikrotik is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx.mikrotik/builds/196 Apr 10 15:23:57 build #203 of cns3xxx is complete: Failure [failed shell_7] Build details are at http://buildbot.openwrt.org:8010/builders/cns3xxx/builds/203 Apr 10 15:33:11 build #206 of ramips.rt305x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt305x/builds/206 Apr 10 15:34:03 build #186 of adm5120 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/186 Apr 10 15:52:24 can sysupgrade display some sort of progressbar during the upgrade stage, when doing upgrade over ethernet ? Apr 10 15:52:37 my understand is it cannot, since the system switches to initrd and cuts off all ethernet connection(s) etc Apr 10 16:37:37 build #189 of mpc85xx is complete: Failure [failed shell_7] Build details are at http://buildbot.openwrt.org:8010/builders/mpc85xx/builds/189 Apr 10 16:37:50 build #216 of kirkwood is complete: Failure [failed shell_18 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/216 Apr 10 16:39:24 build #215 of ar71xx is complete: Failure [failed shell_17] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/215 Apr 10 17:02:05 anyone ? Apr 10 17:03:29 build #209 of brcm47xx.mips74k is complete: Failure [failed shell_17 shell_18] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx.mips74k/builds/209 Apr 10 17:19:18 Marex: it can't Apr 10 17:28:35 jow_laptop: thank you, exactly the sort of yes/no answer I was looking for :) Apr 10 17:29:10 jow_laptop: btw is the DD merge window still open? I have four patches lined up for adding altera socfpga (armv7) support Apr 10 17:52:19 Marex, I think sysupgrade does not cut network connections at least in interactive mode Apr 10 17:52:34 I have runned it via SSH Apr 10 17:53:01 but it uses mtdwrite as backend, so if you want progress bar you have to add it there Apr 10 17:53:49 Necrosporus: isn't interactive mode only interactive before it starts fiddling with the MTD ? Apr 10 17:55:05 it has message like "error fixing mtd header" Apr 10 17:55:12 * TRX Apr 10 17:55:27 So mtd executable's output is still seen Apr 10 17:55:55 I think it does not actually cut local network at all Apr 10 17:56:05 until you let it reboot Apr 10 17:56:58 Necrosporus: do you _think_ so or are you certain ? Apr 10 17:57:06 Necrosporus: also the trx fixup seems to be done before switching to initrd Apr 10 17:58:00 Marex, to be certain I would have to run a sysupgrade again Apr 10 17:58:50 tbh, is that really an issue? :) Apr 10 17:59:07 the progressbar Apr 10 17:59:28 I'm not sure if we need it actually Apr 10 17:59:36 it doesn't take THAT much Apr 10 18:00:55 diizzy: it becomes an issue if the update takes too long Apr 10 18:01:05 diizzy: and that is an issue on newer SPI NOR devices Apr 10 18:01:18 diizzy: they are fast on read, but slow on erase Apr 10 18:01:45 Marex: what is too long? Apr 10 18:02:00 diizzy: minutes Apr 10 18:02:27 my dlink flashes and reboots in like 2-3 minues or so, I fail to set the issue Apr 10 18:02:35 see* Apr 10 18:02:52 diizzy: if the device is in the field, you see nothing for minutes Apr 10 18:03:09 Marex, I am 78% certain that if you add progress bar to mtd then it will be visible Apr 10 18:03:21 Necrosporus: until sshd gets cut off Apr 10 18:03:37 or your vpn Apr 10 18:03:50 I have tried to update with mtd write directly. I have been able to use the device after it finished Apr 10 18:03:52 sshd doesn't get killed, your vpn does however Apr 10 18:04:23 I wasn't able to run programs that were not cached in RAM of course Apr 10 18:05:15 Necrosporus: sorry, that is not the kind of systematic answer I am looking for Apr 10 18:05:35 Marex, so what do you want? Apr 10 18:05:57 do you want to upgrade via web-interface or via ssh? Apr 10 18:06:16 web-if gets shutdown during flashing Apr 10 18:08:52 Necrosporus: I want to update the system via ssh connection via ethernet, but I want to know whether or not it is possible to display some sort of feedback to the user (progress bar or something) or if the ethernet connection gets cut during the upgrade itself Apr 10 18:08:58 mirko: https://dev.openwrt.org/ticket/22048 - any clue? Apr 10 18:09:31 jow_laptop: could you take a look? http://pastebin.com/WCUidgCS Apr 10 18:09:56 Marex: o/ Apr 10 18:11:49 world sure is small :) Apr 10 18:12:11 Marex, I think I have used wi-fi to upgrade Apr 10 18:12:35 and afair it cut wan connection but lan was available Apr 10 18:14:35 Marex, you can include some code to mtd to write a dot each time it erases a block Apr 10 18:14:43 * writes a block Apr 10 18:15:02 it should be simple enough Apr 10 18:16:02 but I guess it's not necessarily a good idea. progress bar takes some cpu time and memory Apr 10 18:17:38 I am not interested in the implementation details, I just want to know whether I can depend on the fact that the ethernet connection will be there during the upgrade or not Apr 10 18:20:40 Marex, in either case you would not want for upgrade process to fail just because ethernet connection was cut Apr 10 18:20:59 it's fairly possible that the user pulls the cable out accidentally Apr 10 18:28:37 no kidding Apr 10 18:28:47 build #183 of omap is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/omap/builds/183 Apr 10 19:00:30 build #251 of ramips.mt7628 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7628/builds/251 Apr 10 19:06:13 build #261 of imx6 is complete: Failure [failed shell_7] Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/261 Apr 10 19:06:57 build #267 of lantiq is complete: Failure [failed shell_18] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/267 Apr 10 19:43:28 build #255 of malta is complete: Failure [failed shell_7] Build details are at http://buildbot.openwrt.org:8010/builders/malta/builds/255 Apr 10 20:14:36 build #186 of sunxi is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/sunxi/builds/186 Apr 10 20:17:16 build #200 of ep93xx is complete: Failure [failed shell_13] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/200 Apr 10 20:17:20 build #217 of kirkwood is complete: Failure [failed shell_18 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/217 Apr 10 21:33:05 build #222 of xburst is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/222 Apr 11 00:36:39 msgctl: apparently you compiled openvpn without management support Apr 11 00:36:53 might be well, that the default binary package is compiled without, as well Apr 11 00:37:17 it's a rather rare use case compared to the additional binary size for the average user Apr 11 00:40:09 openwrt.svn.git$ grep ENABLE_MANAGEMENT ./openwrt.git/trunk/package/network/services/openvpn/Makefile $(if $(CONFIG_OPENVPN_$(BUILD_VARIANT)_ENABLE_MANAGEMENT),--enable,--disable)-management \ Apr 11 00:40:44 looks good to me, if you're sure the option is not included, please send me the full configure and compile output Apr 11 00:43:52 updated the ticket **** ENDING LOGGING AT Mon Apr 11 02:59:58 2016