NAS542 ADMIn login phenomen

frameworker · December 2018

Hi all,

after running a few days or hours (not exactly prooved) the web interface reject any login to the ADMIN account with "account name wrong". To check whether this is right, I've tried to login via ssh.

And it works. So the password is correct.

The workaround is to reboot the whole box via ssh/reboot after login to admin and su -.

I'm working with the most current available firmware. It doesn't matter whether the login happens via firefox, opera or safari or if I using alternative hardware *win 10 box with edge for example.

I think it's a bug. I have tried to restart httpd on the box, but this seems not to make the effort.

Anz ideas or help?

#NAS_Dec_2018

Ijnrsi · December 2018

Even if you reset the device, then problem is still exist?

Mijzelf · December 2018

The webinterface login is managed by samba, while the ssh login is handled by /bin/login.

Samba uses /etc/samba/smbpasswd, while /bin/login uses /etc/shadow.

So the question is: is /etc/samba/smbpasswd changed/damaged when webinterface login no longer works?

frameworker · December 2018

Looks like this:

<div>BusyBox v1.19.4 (2018-05-22 01:24:01 CST) built-in shell (ash)<br>Enter 'help' for a list of built-in commands.<br><br>~ # cd /etc/samba/<br>/etc/samba # ls -l<br>-rw-------&nbsp;&nbsp;&nbsp; 1 root&nbsp;&nbsp;&nbsp;&nbsp; root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 430080 Nov 22 14:59 secrets.tdb<br>-rwxr-xr-x&nbsp;&nbsp;&nbsp; 1 root&nbsp;&nbsp;&nbsp;&nbsp; root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3389 Nov 22 14:59 smb.conf<br>-rwxr-xr-x&nbsp;&nbsp;&nbsp; 1 root&nbsp;&nbsp;&nbsp;&nbsp; root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3167 Nov 22 14:59 smb.conf.bak<br>-rw-------&nbsp;&nbsp;&nbsp; 1 root&nbsp;&nbsp;&nbsp;&nbsp; root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 967 Nov 22 14:59 smbpasswd<br>-rwxr-xr-x&nbsp;&nbsp;&nbsp; 1 1011&nbsp;&nbsp;&nbsp;&nbsp; 1000&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 211 May 21&nbsp; 2018 smbpasswd.default<br>/etc/samba # ps -ef|grep samba<br>ps: invalid option -- 'e'<br>BusyBox v1.19.4 (2018-05-22 01:24:01 CST) multi-call binary.<br><br>Usage: ps <br><br>/etc/samba # ps |grep smbd<br>&nbsp;2969 root&nbsp;&nbsp;&nbsp;&nbsp; 26020 S N&nbsp; /usr/sbin/smbd -D<br>&nbsp;2972 root&nbsp;&nbsp;&nbsp;&nbsp; 26028 S N&nbsp; /usr/sbin/smbd -D<br>22871 root&nbsp;&nbsp;&nbsp;&nbsp; 28888 S N&nbsp; /usr/sbin/smbd -D<br>26314 root&nbsp;&nbsp;&nbsp;&nbsp; 29156 S N&nbsp; /usr/sbin/smbd -D<br>26808 root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2652 S&nbsp;&nbsp;&nbsp; grep smbd<br>/etc/samba # <br>/etc/samba # uptime<br>&nbsp;16:38:14 up 20 days,&nbsp; 1:38,&nbsp; load average: 2.04, 1.55, 1.28<br>/etc/samba # <br><br></div>

I guess smbpasswd was changed the last time I was rebooting the device. ==> Uptime 20 days

So what should I do?

Restarting smbd via /etc/init.d/samba.sh restart doesn't help. Login failed.

The /var/log/samba/smbd.log looks like this:

<div><br></div><div>2018/12/12 15:53:49.874824,&nbsp; 0] ../source3/printing/print_standard.c:68(std_pcap_cache_reload)<br>&nbsp; Unable to open printcap file /etc/printcap for read!<br>[2018/12/12 16:06:51.127661,&nbsp; 0] ../source3/printing/print_standard.c:68(std_pcap_cache_reload)<br>&nbsp; Unable to open printcap file /etc/printcap for read!<br>[2018/12/12 16:19:52.410574,&nbsp; 0] ../source3/printing/print_standard.c:68(std_pcap_cache_reload)<br>&nbsp; Unable to open printcap file /etc/printcap for read!<br>[2018/12/12 16:32:53.660603,&nbsp; 0] ../source3/printing/print_standard.c:68(std_pcap_cache_reload)<br>&nbsp; Unable to open printcap file /etc/printcap for read!<br>[2018/12/12 16:43:15.785678,&nbsp; 0] ../lib/util/pidfile.c:153(pidfile_unlink)<br>&nbsp; Failed to delete pidfile /var/run/smbd.pid. Error was No such file or directory<br>[2018/12/12 16:43:18,&nbsp; 0] ../source3/smbd/server.c:1205(main)<br>&nbsp; smbd version 4.1.7 started.<br>&nbsp; Copyright Andrew Tridgell and the Samba Team 1992-2013<br>[2018/12/12 16:43:18.531197,&nbsp; 0] ../source3/printing/print_standard.c:68(std_pcap_cache_reload)<br>&nbsp; Unable to open printcap file /etc/printcap for read!<br>[2018/12/12 16:44:18.620703,&nbsp; 0] ../source3/printing/print_standard.c:68(std_pcap_cache_reload)<br>&nbsp; Unable to open printcap file /etc/printcap for read!<br></div><div></div>

Mijzelf · December 2018

I guess smbpasswd was changed the last time I was rebooting the device. ==> Uptime 20 days

Yes, that makes sense. The whole /etc directory is on a ramdrive, and on boot the password hashes are restored from some database in flash. So it's not a filesystem action which corrupted smbpasswd.

So what should I do?

Don't know. My knowledge on this matter is not bigger than the last time you asked. https://homeforum.zyxel.com/discussion/comment/2400#Comment_2400

Program a weekly reboot, as work-around?

frameworker · December 2018

Are you sure that samba comes into play when trying to logon?

I've added

 log level = 3 passdb:5 auth:5

to the global section of /etc/samba/smb.conf. After restarting smbd I see nothing. Expecting a lot of data between httpd and possible the samba daemon, but it seems the login process will not use samba?

frameworker · December 2018

I seems samba is only be used when making connections to volumes. I've checked this now.

Then I looked into httdp.conf and found a module called

LoadModule auth_zyxel_module /usr/local/apache/modules/mod_auth_zyxel.so

Mijzelf · December 2018

it seems the login process will not use samba?

Possibly. Don't know how the internals work, it uses smbpasswd. Have a look at /etc/pam.conf, which shows that all services except ssh (and telnet, but I don't think it supports pam), use at least /lib/security/pam_smbpass.so

NAS542 ADMIn login phenomen

All Replies

Categories

Consumer Product Help Center