gsshelton  Freshman Member

Sorry, I'm out of my depth a bit here. When you say the shutdown script, do you mean the sdentware file from the guide? #!/bin/sh /opt/etc/init.d/rc.unslung stop Are you saying overwrite the USRPKG_DEPS_START file in the shutdown script, would I add this as a line? echo entware > /i-data/.system/zy-pkgs/USRPKG_DEPS_START…

Many attempts to get this going, but I can't get any persistence. For some reason every third boot overwrites the content of USRPKG_DEPS_START and breaks the install. My workaround is before a reboot I always check USRPKG_DEPS_START and edit if necessary. I don't see anything in either the start or stop script that would…

I ran echo entware > /i-data/.system/zy-pkgs/USRPKG_DEPS_START again and rebooted and the path came back and I was able to execute opkg commands. But again on reboot it's gone, including the opt dir that had been there.

The instructions are confusing, there really is no need to include this section: touch /i-data/.system/zy-pkgs/USRPKG_DEPS_START chmod +x /i-data/.system/zy-pkgs/USRPKG_DEPS_START echo entware > /i-data/.system/zy-pkgs/USRPKG_DEPS_START It makes it look like that it is what the contents of the USRPKG_DEPS_START needs to…

I removed everything and started over. I get the the step to reboot, the file path exists, I create the shutdown scripts and I'm able to update opkg and install some packages. But then I reboot and the file path is gone, opkg returns an error and USRPKG_DEPS_START has the same code as above. touch…

I spoke too soon. On reboot mount doesn't show the file path anymore and opkg returns an error. So misunderstood the directions and included the following lines in USRPKG_DEPS_START: touch /i-data/.system/zy-pkgs/USRPKG_DEPS_START chmod +x /i-data/.system/zy-pkgs/USRPKG_DEPS_START echo entware >…

USRPKG_DEPS_START was the problem. The guide is confusing on this step. I thought the following needed to be what was in USRPKG_DEPS_START and not just the word entware. touch /i-data/.system/zy-pkgs/USRPKG_DEPS_START chmod +x /i-data/.system/zy-pkgs/USRPKG_DEPS_START echo entware >…

Result of stopping the packages /etc/init.d/zypkg_controller.sh stopStarting "/etc/init.d/zypkg_controller.sh".Stopping all zypkgs via "/etc/init.d/zypkg_controller.sh" ...- shutdowning package "pyLoad" ...grep: pyLoad: No such file or directory---> Error: shutdown program "/etc/init.d/pyLoad" is not existed or not…

I look at the file permissions and this is what is returned -rwxrwxrwx 1 root root 155 Feb 27 14:13 USRPKG_DEPS_STARTlrwxrwxrwx 1 root root 52 Jan 27 22:51 WordPress -> /i-data/ea6cc4e6/.PKG/WordPress/etc/init.d/WordPress-rwxrwxrwx 1 root root 7133479 Jan 27 22:49 WordPress_4.4.1_arm_005.zpkg-rwxrwxrwx 1 root root 10733…

Thanks again for helping me. I ran the command sh -x /i-data/.system/zy-pkgs/entware and this is what was returned:+ VOL=ea6cc4e6 + mkdir -p /i-data/ea6cc4e6/opt+ mkdir -p /opt+ mount -o bind /i-data/ea6cc4e6/opt /opt+ /opt/etc/init.d/rc.unslung start+ echo export PATH=$PATH:/opt/bin:/opt/sbin+ exit 0 I then ran mount…

Maybe I did do some damage when I got serial. I'm noticing that the only LED lighting up is the On light, none of the other lights come on.

It is the Zyxel kernel. I successfully reflashed the latest firmware and tried a powered hub in all three slots, but still no USB connections. There is power going to the USB ports.

Joy! I was able to access it via Safari and I tried another user in Chrome and it worked. I ended up deleting the problem user in Chrome and when I add it back in it works now. @Mijzelf I can't thank you enough for all the time you've taken to help me, it is truly appreciated! I am still having an issue with the USB ports,…

That did correct the http_zld.conf error! That's awesome, thank you! It now boots without that error, but I can't access it via webpage. I can see the samba and afp shares on my network. They both take the admin/1234 user/password, tries to connect and then errors to connection failed. I've attached the output from a…

I've looked at the httpd_zld.conf file that is causing the error and there is a httpd_zld.conf.old file. On lineS 24, 25 & 26 of the .old has listen 80, listen 443, listen 8082, but the current file line 24 has listen none and 25 has listen 8082 and nothing more. But this must just be a symptom of another issue. I change…