Okay, I will reanable the plugin and in future I will check the file after any updates I perform and any changes I make in the plugins config...
Beiträge von Aiakos
-
-
I don't think so unless it was a different drive. Is the path in the grep command correct?
The path is the one that has been used more often in the past (see pictures above). I don't care which path it is, as long as it's always the same one. xD
-
I tried the suggestion in the post above from dinkonin, since I also see the "CRL: cannot read : ..." error. I also tried following the steps in OpenVPN - can't log in. However, I still get the exact same error as posted 4 posts above. Has someone found another soultion in the meantime?
-
Hi, since I dont have direct access to that machine it took me a while, but here is the output:
Coderoot@NAS-Eltern:~# ls /var/lib/openmediavault/rsnapshot.d/ rsnapshot-e97e6ade-e809-48f1-bb9b-9a0bf6c54198.conf root@NAS-Eltern:~# grep snapshot_root /var/lib/openmediavault/rsnapshot.d/* snapshot_root /srv/dev-disk-by-label-Backups/BackupSnapshotsEltern-Share//Backups/BackupEltern-Share//
//Edit: I do also use the LUKS plugin for the backup HDD and unlock it after restart by entering the passphrase in the OMV UI. Can this have any influence on the path?
This is the content of the config file:
# rsnapshot-e97e6ade-e809-48f1-bb9b-9a0bf6c54198.conf
# This configuration file is auto-generated.
# WARNING: Do not edit this file, your changes will be lost.
config_version 1.2
snapshot_root /srv/dev-disk-by-label-Backups/BackupSnapshotsEltern-Share//Backups/BackupEltern-Share//
no_create_root 1 # target root will be created before rsnapshot is running
retain weekly 4
retain monthly 5
verbose 2
loglevel 2
cmd_cp /bin/cp
cmd_rm /bin/rm
cmd_rsync /usr/bin/rsync
cmd_logger /usr/bin/logger
logfile /var/log/rsnapshot.log
rsync_long_args --delete --numeric-ids --delete-excluded
one_fs 0
# no extra destination dir
backup /srv/dev-disk-by-label-Backups/BackupEltern-Share/ ./
rsync_numtries 1
lockfile /var/run/rsnapshot-e97e6ade-e809-48f1-bb9b-9a0bf6c54198.pid -
Today it happened again - it switched back to "Backups" directory in picture 2. This time there were no updates performed and I also did not change anything else on the system. I will disable rsnapshot for now...
Is there anything I can do that might give you a hint on what's going on?
-
I need to bring the topic up again since the problem happened again. As you can see in the pictures, I have rsnapshot running for a while. After I did some updates at 01.09., rsnapshot changed the directory to the one shown in picture 2. After a recent upgrade (yesterday) it now seems to continue with the original directory (picture 1). I dont remember if the updates that I ran contained anything related to the rsnapshot plugin, but there is clearly a glitch here.
Could you have a look into this, please? Using rsnapshot doesn't make much sense if it keeps switching its directories and therefore braking the "timeline"...
-
Apparently, rsnapshot switched back and is now using the old directory again since one week. o_O
I cannot remember that there was an update. Can anyone explain this and how to prevent it from happening again? -
-
If I would be able to go without the backups of the last weeks: Could I just rm the contents of the new directory and cp or mv the contents of the old directory to the new one?
-
Hi Chone,
in the meantime - without having changed anything - I get this new error:
CodeTue Jun 12 19:44:58 2018 VERIFY ERROR: depth=0, error=unsupported certificate purpose: CN=*** Tue Jun 12 19:44:58 2018 OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed Tue Jun 12 19:44:58 2018 TLS_ERROR: BIO read tls_read_plaintext error Tue Jun 12 19:44:58 2018 TLS Error: TLS object -> incoming plaintext read error Tue Jun 12 19:44:58 2018 TLS Error: TLS handshake failed
What does this mean?
-
No suggestions?
-
Hi everybody,
I had OpenVPN working under OMV3 perfectly for quite a long time. After the upgrade to OMV4, I reinstalled the plugin and created new a new certificate for my client using the GUI. If I now try to connect the client, I get the error mentioned above:
Wed Jun 06 20:36:31 2018 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 26 2018
Wed Jun 06 20:36:31 2018 Windows version 6.2 (Windows 8 or greater) 64bit
Wed Jun 06 20:36:31 2018 library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10
Wed Jun 06 20:36:31 2018 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25341
Wed Jun 06 20:36:31 2018 Need hold release from management interface, waiting...
Wed Jun 06 20:36:31 2018 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25341
Wed Jun 06 20:36:31 2018 MANAGEMENT: CMD 'state on'
Wed Jun 06 20:36:31 2018 MANAGEMENT: CMD 'log all on'
Wed Jun 06 20:36:31 2018 MANAGEMENT: CMD 'echo all on'
Wed Jun 06 20:36:31 2018 MANAGEMENT: CMD 'bytecount 5'
Wed Jun 06 20:36:31 2018 MANAGEMENT: CMD 'hold off'
Wed Jun 06 20:36:31 2018 MANAGEMENT: CMD 'hold release'
Wed Jun 06 20:36:31 2018 MANAGEMENT: >STATE:***,RESOLVE,,,,,,
Wed Jun 06 20:36:31 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]***.***.***.***:1194
Wed Jun 06 20:36:31 2018 Socket Buffers: R=[65536->65536] S=[65536->65536]
Wed Jun 06 20:36:31 2018 UDP link local: (not bound)
Wed Jun 06 20:36:31 2018 UDP link remote: [AF_INET]***.***.***.***:1194
Wed Jun 06 20:36:31 2018 MANAGEMENT: >STATE:***,WAIT,,,,,,
Wed Jun 06 20:36:31 2018 MANAGEMENT: >STATE:***,AUTH,,,,,,
Wed Jun 06 20:36:31 2018 TLS: Initial packet from [AF_INET]***.***.***.***:1194, sid=***
Wed Jun 06 20:36:31 2018 VERIFY OK: depth=1, CN=ChangeMe
Wed Jun 06 20:36:31 2018 VERIFY KU OK
Wed Jun 06 20:36:31 2018 Validating certificate extended key usage
Wed Jun 06 20:36:31 2018 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Wed Jun 06 20:36:31 2018 VERIFY EKU OK
Wed Jun 06 20:36:31 2018 VERIFY OK: depth=0, CN=NASWhat can I do?
Best,
Aiakos -
Hi everybody,
two weeks ago I updated from OMV 3 to 4 without any problems. Since then, rsnapshot uses a different directory in my backup share and thus builds up new snapshots from scratch. I now have one folder with the old snapshots:
Coderoot@NAS:/sharedfolders# ls BackupSnapshots-Share/HT750/Backup-Share/ daily.0 daily.11 daily.2 daily.5 daily.8 monthly.1 monthly.4 weekly.1 weekly.2 weekly.5 weekly.8 daily.1 daily.12 daily.3 daily.6 daily.9 monthly.2 monthly.5 weekly.10 weekly.3 weekly.6 weekly.9 daily.10 daily.13 daily.4 daily.7 monthly.0 monthly.3 weekly.0 weekly.11 weekly.4 weekly.7
And a new one where the snapshots now get created:Coderoot@NAS:/sharedfolders# ls BackupSnapshots-Share/media/c486d52a-****-****-****-***********/Backup-Share/ daily.0 daily.1 daily.10 daily.11 daily.2 daily.3 daily.4 daily.5 daily.6 daily.7 daily.8 daily.9
Since I know that rsanpshot uses hardlinks in order to create incremental snapshots, I am afraid to break something if I just copy the folders from the old location to the new one. What is the recommended way to proceed in this case? Or is it even possible to have rsnapshot use the old directory again?Best,
Aiakos -
Got it! I created a new dummy share and then the bind mounts for all existing shares were created automatically. Thank you!
-
Hi everbody,
I recently upgraded two NAS systems from OMV 3 to 4 using omv-release-upgarde. Both upgrades went just fine, I am very happy - thanks for the hard work!! However, ob both systems there is a new directory /sharedfolders, which is empty. I guess it is supposed to acces shared folders directly, right? What do I need to do in oder to make this work?
Best,
Aiskos -
Problem solved:
/var/spool/postfix/etc/resolv.conf
and
/etc/resolv.conf
were not identical. In fact, the first one was empty (except for two lines of comments). A reboot solved this. -
Hi everone!
After I upgraded to 3.0.98 yesterday, e-mail notifications stopped working. The log says:
status=deferred (Host or domain name not found. Name service error for name=smtp.web.de type=MX: Host not found, try again)I don't know if this problem is related to the version upgrade. I did not change anything else and I can ping smtp.web.de using the terminal. Any ideas?
Best,
Aiakos -
Double posting - please delete.
-
So far I have saved 4 syslogs of a normal shutdown / reboot and 1 syslog of a shutdown where the system got stuck.
Normal:
systemd[1]: Starting Beep before system shutdown...
systemd[1]: Unmounting /media/...
systemd[1]: Unmounting /media/...
systemd[1]: Unmounting /media/...
systemd[1]: Unmounting /media/...
systemd[1]: Stopping Sound Card.
systemd[1]: Stopped target Sound Card.
systemd[1]: Stopping system-ifup.slice.
systemd[1]: Removed slice system-ifup.slice.
systemd[1]: Stopping system-systemd\x2dfsck.slice.
systemd[1]: Removed slice system-systemd\x2dfsck.slice.
systemd[1]: Stopping RPC Port Mapper.
systemd[1]: Stopped target RPC Port Mapper.
systemd[1]: Stopping Graphical Interface.
systemd[1]: Stopped target Graphical Interface.
systemd[1]: Stopping Multi-User System.
systemd[1]: Stopped target Multi-User System.
systemd[1]: Stopping OpenBSD Secure Shell server...
systemd[1]: Stopping The PHP FastCGI Process Manager...
systemd[1]: Stopping ClamAV virus database updater...
systemd[1]: Stopping The OpenMediaVault engine daemon that processes the RPC request...
systemd[1]: Stopping Self Monitoring and Reporting Technology (SMART) Daemon...
systemd[1]: Stopping A high performance web server and a reverse proxy server...
systemd[1]: Stopping Initialize hardware monitoring sensors...
systemd[1]: Stopped Initialize hardware monitoring sensors.
systemd[1]: Stopping Regular background program processing daemon...
systemd[1]: Stopping Login Service...
systemd[1]: Stopping Login Prompts.
systemd[1]: Stopped target Login Prompts.
systemd[1]: Stopping Getty on tty1...
systemd[1]: Stopping LSB: start Samba daemons for the AD DC...
systemd[1]: Stopping LSB: manage the statistics collection daemon...
systemd[1]: Stopping Mail Transport Agent.
systemd[1]: Stopped target Mail Transport Agent.
systemd[1]: Stopping LSB: Postfix Mail Transport Agent...
systemd[1]: Stopping LSB: HPA's tftp server...
systemd[1]: Stopping LSB: service and resource monitoring daemon...
systemd[1]: Stopping LSB: start Samba SMB/CIFS daemon (smbd)...
systemd[1]: Stopping LSB: start the RRDtool data caching daemon...
rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="1129" x-info="http://www.rsyslog.com"] exiting on signal 15.Stuck:
systemd[1]: Starting Beep before system shutdown...
systemd[1]: Unmounting /media/...
systemd[1]: Unmounting /media/...
systemd[1]: Unmounting /media/...
systemd[1]: Unmounting /media/...
systemd[1]: Stopping system-ifup.slice.
systemd[1]: Removed slice system-ifup.slice.
systemd[1]: Stopping Sound Card.
systemd[1]: Stopped target Sound Card.
systemd[1]: Stopping RPC Port Mapper.
systemd[1]: Stopped target RPC Port Mapper.
systemd[1]: Stopping system-systemd\x2dfsck.slice.
systemd[1]: Removed slice system-systemd\x2dfsck.slice.
systemd[1]: Stopping Graphical Interface.
systemd[1]: Stopped target Graphical Interface.
systemd[1]: Stopping Multi-User System.
systemd[1]: Stopped target Multi-User System.
systemd[1]: Stopping OpenBSD Secure Shell server...
systemd[1]: Stopping The PHP FastCGI Process Manager...
systemd[1]: Stopping ClamAV virus database updater...
systemd[1]: Stopping The OpenMediaVault engine daemon that processes the RPC request...
systemd[1]: Stopped The OpenMediaVault engine daemon that processes the RPC request.
systemd[1]: Stopping Self Monitoring and Reporting Technology (SMART) Daemon...
systemd[1]: Stopping A high performance web server and a reverse proxy server...
systemd[1]: Stopping Initialize hardware monitoring sensors...
systemd[1]: Stopped Initialize hardware monitoring sensors.
systemd[1]: Stopping Regular background program processing daemon...
systemd[1]: Stopping Login Service...
systemd[1]: Stopping Login Prompts.
systemd[1]: Stopped target Login Prompts.
systemd[1]: Stopping Getty on tty1...
systemd[1]: Stopping LSB: start Samba daemons for the AD DC...
systemd[1]: Stopping LSB: manage the statistics collection daemon...
systemd[1]: Stopping Mail Transport Agent.
systemd[1]: Stopped target Mail Transport Agent.
systemd[1]: Stopping LSB: Postfix Mail Transport Agent...
systemd[1]: Stopping LSB: HPA's tftp server...
systemd[1]: Stopping LSB: service and resource monitoring daemon...
systemd[1]: Stopping LSB: start Samba SMB/CIFS daemon (smbd)...
systemd[1]: Stopping LSB: start the RRDtool data caching daemon...
systemd[1]: Stopping LSB: Start NTP daemon...
systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
systemd[1]: Stopping D-Bus System Message Bus...
systemd[1]: Stopping ACPI event daemon...
systemd[1]: Stopping System Logging Service...
systemd[1]: Starting folder2ram systemd service...
rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="1118" x-info="http://www.rsyslog.com"] exiting on signal 15.The only real difference between the two logs are the 5 lines at the end of the log where the system got stuck:
Codesystemd[1]: Stopping Avahi mDNS/DNS-SD Stack... systemd[1]: Stopping D-Bus System Message Bus... systemd[1]: Stopping ACPI event daemon... systemd[1]: Stopping System Logging Service... systemd[1]: Starting folder2ram systemd service...
I was not able to find these lines in any of the logs, where the system shut down normally. Does this mean anything?
-
Sorry, maybe I did not explain it very well. What I meant was that the disk gets auto mounted after I unlock it, but the systems waits for the timeout on boot. I can avoid this timeout by adding "noauto" to fstab, but then the disk does not get mounted automatically any more, after I unlock it. My question was how I can have both auto mounting and no timeout on boot.
Your suggestion regarding reducing the timeout to two 2 seconds seems to work. Thus, I consider the problem to be solved. Thank you!