Beiträge von wolffstarr

Zitat von hensur

Hello,
I had the same problem until yesterday, on a clean install of openmediavault with the latest ISO from December 2016. Services like samba wouldn't start when using systemd or the init.d script. The binary itself could be run without any problems.
I noticed that there are two start-stop-daemons: /sbin/start-stop-daemon and /sbin/start-stop-daemon.REAL
I fixed the problem by moving /sbin/start-stop-daemon.REAL to /sbin/start-stop-daemon. Now everything works fine.

Oh wow. That's... really funky. Time to go check.

Zitat von ryecoaaron

I don't have two start-stop-daemon files on any of my systems. No idea what creates it but it would interesting to know.

It was definitely the same image I used, I think 3.0.58 or something like that - I'd have to dig it out.

Yep, had that happen a few times myself. There's a way around it with normal filesystems that mount through fstab, but since ZFS mounts are done differently it can get caught up if something causes it to get unmounted.

Glad it's working for ya!

Well, for a quick fix, try zfs mount mainpool manually. I'm assuming you only have the base mainpool dataset and no child datasets.

I'm about to leave for work, but I've had a similar problem in the past; I'll try to track down some info for you.

If zfs mount mainpool doesn't work, it should give a useful error. Also, make sure there's nothing in the /mainpool directory that it mounts to; that can cause issues as well.

Was this after a reboot?

What is the output of zfs list and df -h from the command line?

If you can't get at the command line, what does the File Systems page show? You should be seeing Mounted = Yes for everything.

Zitat von ryecoaaron

Latest package in same location has the inotify stuff in it. I think it should be close to ready.

That, I'm going to have to set up a test VM for. Don't want to revert the changes on the live boxes now that I've got it just so. Should be able to do it later tonight.

Alright, got it rebooted, not sure what exactly happened but the system was running, it just didn't have a network connection somehow. networking.service fails to run, which I'm beginning to think may be the root of the problem altogether. Note that network-online.target is fine, and I'm (now) able to access remotely over SSH and the web UI, but networking.service is down. Here's the status output:

root@mjolnir:~# systemctl status networking
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/generator/networking.service.d
           └─50-insserv.conf-$network.conf
   Active: failed (Result: exit-code) since Sat 2017-03-11 21:40:26 EST; 14min ago
     Docs: man:interfaces(5)
 Main PID: 6239 (code=exited, status=1/FAILURE)


Mar 11 21:40:25 mjolnir ifup[6239]: RTNETLINK answers: File exists
Mar 11 21:40:25 mjolnir ifup[6239]: bound to 192.168.1.133 -- renewal in 33111 seconds.
Mar 11 21:40:26 mjolnir ifup[6239]: ifquery: recursion detected for interface eth0 in post-up phase
Mar 11 21:40:26 mjolnir ifup[6239]: run-parts: /etc/network/if-up.d/openmediavault-issue exited with return code 1
Mar 11 21:40:26 mjolnir ifup[6239]: Failed to bring up eth0.
Mar 11 21:40:26 mjolnir ifup[6239]: invoke-rc.d: action alarm is unknown, but proceeding anyway.
Mar 11 21:40:26 mjolnir systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Mar 11 21:40:26 mjolnir systemd[1]: Failed to start Raise network interfaces.
Mar 11 21:40:26 mjolnir systemd[1]: networking.service: Unit entered failed state.
Mar 11 21:40:26 mjolnir systemd[1]: networking.service: Failed with result 'exit-code'.
root@mjolnir:~#

Now, that was the result of me trying to enable IPv6 via the web UI, but I just issued a systemctl start networking.service and the only thing that changed was the timestamps. On the other hand, that might be something from sysvinit and this is an effect of the issue, not a cause.

On the plugin updates for Syncthing, uploaded the new one, I've got the enable switch for inotify now, and it works if I create with it (and doesn't if I don't), shuts off if I disable, comes up when I enable, and all around works as I'd expect it to.

Zitat von ryecoaaron

Just need to figure out where to set the max user watches.

It's in /etc/sysctl.conf, needs to have fs.inotify.max_user_watches=204800 to make the change permanent, but to change it for the running system, /proc/sys/fs/inotify/max_user_watches is what needs to be set to 204800. Syncthing's github page tells you to use the command sudo sh -c 'echo 204800 > /proc/sys/fs/inotify/max_user_watches' to set it, and it needs to be done prior to starting inotify.

Haven't had a chance to test yet, I rebooted the remote NAS earlier for something else and it never came back online. When/if I can get a hard reboot and make sure there's power to it, I'll update and test.

Thanks!

Zitat von ryecoaaron

New version in same location.

Gotcha, will give it a spin shortly.

Random thought, I was able to bring my CPU utilization WAAAAAY down - like, average of 15% to about 0.1% - by installing syncthing-inotify along with it. Only problem is, it pretty well chews through the inotify queue and you have to modify /etc/sysctl.conf to increase it. Not exactly a good idea for a plugin, but if you've got a weaker system using Syncthing, might make a huge difference.

Zitat von ryecoaaron

Maybe try reinstalling systemd-sysv and sysvinit-utils?

Might as well. I'd tried apt-get install --reinstall samba to see if I could get it to rebuild the sysv script-generated unit, but that didn't impact. Might as well do the same thing with those.

Zitat von ryecoaaron

Thanks for pointing that out. Deleted users are disabled now. If you want to try the latest package, it is available in the same place.

Yep, that took care of it. I note that when I deleted the test user, the regular user's web UI became unavailable for about 30 seconds to a minute. I mention it more as a head's up for when someone says "OMG I DELETED $OLDUSER AND YOU DELETED $CURRENTUSER TOO!!!!11!!eleven1!".

Any ideas as to what could be causing pretty much every SysV-controlled script to be blowing up? I've compared scripts between the two boxes and I come up with nothing really different.

Zitat von ryecoaaron

If you want to try my latest change to using the systemd unit file instead of my init script, you can download the package here.

Okay, first thing's first: It works just fine for me. Uninstalled Syncthing and plugin, manually deleted the config files after backing them up for the users I was using, manually reinstalled syncthing then did a purge of it (just in case), then reinstalled via OMV WebUI and went in.

First I created a dummy one with a different user on different ports from the default. Applied no problem, Syncthing GUI came up right away. Deleted that dummy user, set one up for my original user on the default ports, and for a minute or so I was getting connection refused. Then the UI with mapped folders, Username/Password prompt, and changed theme just like it was before testing popped up. Clearly there's somewhere other than ~/.config/syncthing/ that the user configs are saved.

On a momentary whim, however, I went back to the port that I used for the dummy user, and it was still up and running. Given how heavy scans and syncs can be, that could be bad.

Other than that, seems to be working just fine.

I'll give that a whirl later tonight or tomorrow once I have a bit to play with it.

It does, since Syncthing is designed to be per-user sync like Dropbox is. The service it uses is syncthing@.service, and the username running the process goes after the @.

What I can't figure out is why none of the sysvinit wrapped services appear to be working. I'm also more than slightly surprised that Samba doesn't have a native systemd service file, though I wouldn't be shocked to find that that's Debian being a bit lagged.

So, poking around some more, not really trying to "solve" the issue, but just because I can't leave it alone, I tried to figure out why manually doing systemctl start syncthing@root.service worked where systemctl start syncthing.service didn't, I discovered that the former is Syncthing's native systemd setup, whereas the latter is a sysvinit wrapper that systemd uses.

So, looking into it, tftpd-hpa, smbd, and probably xrdp are all using sysvinit scripts and systemd-sysv-install as a wrapper to let systemd control it.

I have no idea WHY sysvinit scripts aren't properly running, but that's what looks like is going on. Any thoughts?

Zitat von ryecoaaron

How did you install Linux/OMV without creating a root account? sudo is an Ubuntu idea. Debian uses root. Why are you not using the OMV ISO?

Er... just for the record, sudo is way older than Ubuntu and I use it in Debian (and OMV) all the time. It's in fact recommended practice across all Linux distros to NOT use root and instead use sudo.

The difference being, Ubuntu doesn't even have a root password setup by default. The account's there but they go out of their way to avoid using it.

That said, yeah, it sounds like something strange is in use here.

Zitat von ryecoaaron

Unfortunately, that didn't show me any problems. I guess I am back to maybe bad ram?

Two 4GB ECC UDIMMs in the box. I guess it COULD be, but it was running in my main NAS without issues. Unfortunately, running memtest86 on it is non-trivial. On the other hand, Samba is a nice-to-have in this situation, so as long as I can get syncthing running. I'll track it down eventually.

Thanks for the help!

Zitat von ryecoaaron

Longer posts sometimes trigger the spam filter. I approved it.

Didn't find anything odd in your output. How about dpkg -l | grep samba

Here we go; heading home now (had a night maintenance) so won't be able to reply until much later, if at all tonight.

wolfstar@mjolnir:~$ dpkg -l | grep samba
ii  python-samba                       2:4.2.14+dfsg-0+deb8u2     amd64        Python bindings for Samba
ii  samba                              2:4.2.14+dfsg-0+deb8u2     amd64        SMB/CIFS file, print, and login server for Unix
ii  samba-common                       2:4.2.14+dfsg-0+deb8u2     all          common files used by both the Samba server and client
ii  samba-common-bin                   2:4.2.14+dfsg-0+deb8u2     amd64        Samba common files used by both the server and the client
ii  samba-dsdb-modules                 2:4.2.14+dfsg-0+deb8u2     amd64        Samba Directory Services Database
ii  samba-libs:amd64                   2:4.2.14+dfsg-0+deb8u2     amd64        Samba core libraries
ii  samba-vfs-modules                  2:4.2.14+dfsg-0+deb8u2     amd64        Samba Virtual FileSystem plugins
wolfstar@mjolnir:~$

Thanks Ryecoaaron!

For some reason it's telling me the post I made about an hour ago requires approval by a moderator. It did throw an error, but on refresh it was present.

Let me know if you need me to repost.

Here you go:

wolfstar@mjolnir:~$ ls -al /var/log/
total 3080
drwxr-xr-x 11 root root   4096 Mar  6 07:35 .
drwxr-xr-x 12 root root   4096 Mar  2 00:10 ..
-rw-r--r--  1 root root   9488 Mar  7 10:42 alternatives.log
drwxr-xr-x  2 root root   4096 Mar  2 00:10 apt
-rw-r-----  1 root adm  125259 Mar  7 18:53 auth.log
-rw-r-----  1 root adm  112665 Mar  5 11:12 auth.log.1
-rw-r--r--  1 root root      0 Dec 29 06:40 bootstrap.log
-rw-------  1 root utmp   2304 Mar  2 13:49 btmp
drwxr-xr-x  2 root root   4096 Mar  5 00:23 cron-apt
-rw-r-----  1 root adm  195977 Mar  7 17:30 daemon.log
-rw-r-----  1 root adm  415422 Mar  5 11:12 daemon.log.1
-rw-r-----  1 root adm   35350 Mar  7 10:30 debug
-rw-r-----  1 root adm   89788 Mar  5 00:18 debug.1
-rw-r-----  1 root adm       0 Dec 29 06:40 dmesg
-rw-r--r--  1 root root 346984 Mar  7 10:44 dpkg.log
-rw-r--r--  1 root root  32064 Mar  5 01:13 faillog
-rw-r--r--  1 root root   1220 Mar  7 10:44 fontconfig.log
drwxr-xr-x  2 root root   4096 Mar  2 00:10 fsck
-rw-r-----  1 root adm  146308 Mar  7 12:16 kern.log
-rw-r-----  1 root adm  364469 Mar  5 09:49 kern.log.1
-rw-rw-r--  1 root utmp 292584 Mar  7 18:53 lastlog
-rw-r-----  1 root adm    8193 Mar  7 18:17 mail.err
-rw-r-----  1 root adm    1825 Mar  3 00:17 mail.err.1
-rw-r-----  1 root adm    8193 Mar  7 18:17 mail.info
-rw-r-----  1 root adm    2409 Mar  3 00:17 mail.info.1
-rw-r-----  1 root adm    8193 Mar  7 18:17 mail.log
-rw-r-----  1 root adm    2409 Mar  3 00:17 mail.log.1
-rw-r-----  1 root adm    8193 Mar  7 18:17 mail.warn
-rw-r-----  1 root adm    2409 Mar  3 00:17 mail.warn.1
-rw-r-----  1 root adm  120200 Mar  7 12:16 messages
-rw-r-----  1 root adm  289882 Mar  5 11:12 messages.1
-rw-r-----  1 root adm       0 Mar  7 09:20 monit.log
drwxr-xr-x  2 root adm    4096 Mar  5 00:23 nginx
drwxr-xr-x  2 root root   4096 Mar  2 00:14 openmediavault
-rw-------  1 root root    814 Mar  7 10:30 php5-fpm.log
-rw-------  1 root root   2178 Mar  5 00:19 php5-fpm.log.1
drwxr-xr-x  2 root root   4096 Mar  2 00:10 proftpd
drwxr-x---  2 root adm    4096 Dec 17 16:20 samba
drwxr-xr-x  2 root root   4096 Mar  5 01:14 syncthing
-rw-r-----  1 root adm  161784 Mar  7 18:45 syslog
-rw-r-----  1 root adm  272890 Mar  7 09:18 syslog.1
-rw-r-----  1 root adm  134836 Mar  5 11:12 syslog.2.gz
-rw-r--r--  1 root root  63936 Mar  7 10:40 tallylog
-rw-r-----  1 root adm   10632 Mar  7 08:28 user.log
-rw-r-----  1 root adm   66304 Mar  2 04:28 user.log.1
drwxr-xr-x  2 root root   4096 Dec  4  2014 watchdog
-rw-rw-r--  1 root utmp  43392 Mar  7 18:53 wtmp
wolfstar@mjolnir:~$

On the assumption you'd want it as well, there's nothing in /var/log/samba:

wolfstar@mjolnir:/var/log/samba$ ls -al
total 8
drwxr-x---  2 root adm  4096 Dec 17 16:20 .
drwxr-xr-x 11 root root 4096 Mar  6 07:35 ..
wolfstar@mjolnir:/var/log/samba$

Confirmed, JUST in case, that it's also empty for root (sudo).

Works for me. As a note - and I have no idea why this is - I was able to do "systemctl enable syncthing@user.service" and "systemctl start syncthing@user.service" and syncthing is functioning now. I did NOT need to do that on my main NAS, and trying to do systemctl status syncthing@user.service" comes back with the result that it's dead, despite that being the user it's running as, so clearly something weird going on here.

On to SMB, here's the output for smbd.service:

wolfstar@mjolnir:~$ systemctl status smbd.service
● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd)
   Loaded: loaded (/etc/init.d/smbd; generated; vendor preset: enabled)
   Active: active (exited) since Tue 2017-03-07 10:45:41 EST; 1h 1min ago
     Docs: man:systemd-sysv-generator(8)
   CGroup: /system.slice/smbd.service


Mar 07 10:45:40 mjolnir systemd[1]: Starting LSB: start Samba SMB/CIFS daemon (smbd)...
Mar 07 10:45:41 mjolnir smbd[5792]: Starting SMB/CIFS daemon: smbd.
Mar 07 10:45:41 mjolnir systemd[1]: Started LSB: start Samba SMB/CIFS daemon (smbd).
wolfstar@mjolnir:~$

And here's nmbd.service:

wolfstar@mjolnir:~$ systemctl status nmbd.service
● nmbd.service - LSB: start Samba NetBIOS nameserver (nmbd)
   Loaded: loaded (/etc/init.d/nmbd; generated; vendor preset: enabled)
   Active: active (exited) since Tue 2017-03-07 10:30:24 EST; 1h 17min ago
     Docs: man:systemd-sysv-generator(8)
   CGroup: /system.slice/nmbd.service


Mar 07 10:30:07 mjolnir systemd[1]: Starting LSB: start Samba NetBIOS nameserver (nmbd)...
Mar 07 10:30:24 mjolnir nmbd[3174]: Starting NetBIOS name server: nmbd.
Mar 07 10:30:24 mjolnir systemd[1]: Started LSB: start Samba NetBIOS nameserver (nmbd).
wolfstar@mjolnir:~$

Note in both cases the "active (exited)" is in green text.

Syncthing isn't even configured - the only time I got it to run was running it on the command line.

Update went all Hulk on my VPN connection (TINC SMASH!) and I had to back door into it via port forwarding on my parents' router (thank goodness for "Linksys Smart Wifi"). Reboot restored that, and SSH never stopped working or I'd really be hosed, but the reboot did not start up SMB, Syncthing, TFTP, or XRDP.

Just to try it, I'm going through and removing plugins I don't really need. In this case, it's Sensors (which didn't work anyhow; errors every time I try and apply configs - sensors command in shell works just fine though), Remote-mount, remotedesktop, and locate.

Nope, still won't run. I was kind of hoping this would get somewhere since the update included a change from Systemd 215 to 230, but doesn't look like it.