It seems like I am having issues with the urbackup-server not wanting to listen on the set port of 55414 or 55415 for the web interface. My Docker transmission is fine. I run netstat -tap | grep 55414, and get a blank line in return. I've added an incoming rule for those ports. Still nothing. Its like the service is failing to listen on those ports. No number of restarting of the service brings it up. lsof -i :55415 also brings back a blank line. I love a puzzle, but this sure is a conundrum. Oh go easy on me too, its my first time posting here!
urBackkup Plugin
-
- OMV 4.x
- soulreaper11207
-
-
Looks like it had updated to Debian 4.18 on me. I was able to revert back to 4.14 via grub selection, but now I'm wondering how to remove the 4.18 entry, or change the auto selection.
-
Nope still not working right.
-
-
Within OMV Extras, kernel tab, you can set the default kernel.
-
I just removed the entries in grub. Now it boots into the proper kernal. Did a reinstall of the urbackup-server plugin, but it still isnt listening on the configured ports.
-
So I guess just do a reinstall of OMV? Maybe the accidental up date of the kernal is causing issues with the service not listening on the configured port?
-
-
Did a complete system reinstall, updated the models, uploaded omv-extras, installed the plugin, refreshed, installed the server-urbackup, changed the webport by one to 55415, and still no dice. Does anyone have any ideas?
-
Have you enabled the service?
Post a screen shot of your "General Settings" of the Urbackup service and the output of
systemctl status urbackupsrv.service
and
sudo lsof -i -P -n | grep urback -
I enabled it through the Services tab on OMV's webinterface.
root@openmediavault:~# systemctl status urbackupsrv.service
● urbackupsrv.service - LSB: Server for doing backups
Loaded: loaded (/etc/init.d/urbackupsrv; generated; vendor preset: enabled)
Active: active (exited) since Fri 2019-01-25 23:27:12 EST; 18h ago
Docs: man:systemd-sysv-generator(8)
Process: 1949 ExecStart=/etc/init.d/urbackupsrv start (code=exited, status=0/S
UCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/urbackupsrv.serviceWarning: Journal has been rotated since unit was started. Log output is incomplete
or unavailable.sudo lsof -i -P -n | grep urback
Returns a blank line.And then I got a bunch of these in the syslog when I restarted the daemon.
Jan 26 00:05:52 openmediavault collectd[866]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect to rrdcached: No such file or directory (status=2)I also included a snipit of the system info on my dashboard. Let me know if you need anything else.
-
-
Active: active (exited) since Fri 2019-01-25 23:27:12 EST; 18h ago
The service is not running any more. It says "exited", but it should be "running".
What is the output of
systemctl start urbackupsrv.service? That should start the service. -
There was no output when I ran that. Ran the status check for the service and it still says active (exited). Same with running service urbackupsrv start.
-
Have you checked the logs in the GUI of OMV? "Syslog", "UrBackup server" and "Messages"
-
-
Messages is blank, Urbackup displays error that says unable to open file, and syslog has a bunch of lines that I had mentioned before.
Jan 26 00:05:52 openmediavault collectd[866]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect to rrdcached: No such file or directory (status=2)
-
Urbackup displays error that says unable to open file
What is the exact message?
-
Failed to open the log file (filename=/var/log/urbackup.log).
Details:
Error #0:OMV\Exception: Failed to open the log file (filename=/var/log/urbackup.log). in /usr/share/openmediavault/engined/rpc/logfile.inc:77Stack trace:#0 [internal function]: OMVRpcServiceLogFile->getList(Array, Array)#1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#2 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getList', Array, Array)#3 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('LogFile', 'getList', Array, Array, 1)#4 {main} -
-
No idea, what went wrong.
changed the webport by one to 55415
Why did you change the port?
What is the output of dpkg -l | grep urbackup
-
root@openmediavault:~# dpkg -l | grep urbackupii openmediavault-urbackup-server 3.1 all OpenMediaVault urbackup-server pluginii urbackup-server 2.3.7.0-1 amd64 Server for backing up clients
It was a recommended action in one of the urbackup forums.
-
That looks fine.
Do you have /var/log/urbackup.log?
It should be owned by user/group urbackup
-rw-r----- 1 urbackup urbackup 0 Jan 27 00:05 urbackup.log
-
-
It seems your problem is not that urbackup is not listening on the correct port, but the service is exited.
-
No log in that file location. So how do we fix the service?
https://unix.stackexchange.com…mean-for-a-custom-service
according to this the active exit status means nothing unless you set it to monitor the daemon?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!