apt-get purge openmediavault-flashmemory folder2ram
reboot
mkdir -p /var/log/{cron-apt,nginx}
reboot
Is everything working now?
apt-get purge openmediavault-flashmemory folder2ram
reboot
mkdir -p /var/log/{cron-apt,nginx}
reboot
Is everything working now?
Thank you so much! Yes it works now
Obviously something is deleting all of sub-directories in /var/log causing this problem. I would purge openmediavault-flashmemory and folder2ram, create the directories, and see if it works after reboot. If that is working, then re-install flashmemory.
As you wrote in an earlier post; "If that is working, then re-install flashmemory.". If I did what you said, is flashmemory reinstalled too?
is flashmemory reinstalled too?
Nope. I wanted to get the system back to working condition. Now post the output of:
omv-aptclean
apt-cache policy openmediavault-flashmemory folder2ram
Aaaah! Here is the output:
ZitatAlles anzeigen$ sudo apt-cache policy openmediavault-flashmemory folder2ram
openmediavault-flashmemory:
Installed: (none)
Candidate: 5.0.7
Version table:
5.0.7 500
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages
100 /var/lib/dpkg/status
5.0.6 500
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages
5.0.5 500
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages
5.0.4 500
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages
5.0.3 500
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages
5.0.2 500
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages
5.0.1 500
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages
5.0 500
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages
folder2ram:
Installed: 0.3.3
Candidate: 0.3.3
Version table:
*** 0.3.3 500
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages
100 /var/lib/dpkg/status
0.3.1 500
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main arm64 Packages
500 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf Packages
$
Here is the output:
Interesting that I had you purge folder2ram in a previous step but it is still installed. Did you re-install it? Either way, you should be able to reinstall the flashmemory plugin from the web interface now.
No, I haven't reinstalled anything. Hm...
I just reinstalled the flashmemory plugin in the GUI and rebooted. Now the GUI is unavaliable again. Received a couple of e-mails too... Ha-ha, wtf?!
just reinstalled the flashmemory plugin in the GUI and rebooted. Now the GUI is unavaliable again. Received a couple of e-mails too... Ha-ha, wtf?!
Your folder2ram install must not be configured and that is why it works when the flashmemory plugin is not install. Go through the steps again but make sure folder2ram is purged.
Sorry, I didn't read the log properly earlier...
This is what happens when trying to purge folder2ram:
$ sudo apt-get purge openmediavault-flashmemory folder2ram
[sudo] password for mariusenglund:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
folder2ram* openmediavault-flashmemory*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 245 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 53315 files and directories currently installed.)
Removing openmediavault-flashmemory (5.0.7) ...
will now sync all mountpoints
/var/log unmounted, cannot comply
sync of /var/tmp successful!
sync of /var/lib/openmediavault/rrd successful!
sync of /var/spool successful!
sync of /var/lib/rrdcached successful!
sync of /var/lib/monit successful!
sync of /var/cache/samba successful!
will now stop all mountpoints
stop /var/log
/var/log already unmounted
stop /var/tmp
stop /var/lib/openmediavault/rrd
stop /var/spool
stop /var/lib/rrdcached
stop /var/lib/monit
stop /var/cache/samba
Warning: Can't execute disable on the unit file path. Proceeding with the unit name.
Removed /etc/systemd/system/basic.target.wants/folder2ram_startup.service.
Warning: Can't execute disable on the unit file path. Proceeding with the unit name.
Removed /etc/systemd/system/shutdown.target.wants/folder2ram_shutdown.service.
Removed /etc/systemd/system/reboot.target.wants/folder2ram_shutdown.service.
Removed /etc/systemd/system/halt.target.wants/folder2ram_shutdown.service.
Removing folder2ram (0.3.3) ...
/sbin/folder2ram: 980: /sbin/folder2ram: insserv: not found
/sbin/folder2ram: 996: /sbin/folder2ram: insserv: not found
dpkg: error processing package folder2ram (--remove):
installed folder2ram package pre-removal script subprocess returned error exit status 127
Errors were encountered while processing:
folder2ram
E: Sub-process /usr/bin/dpkg returned an error code (1)
$
Alles anzeigen
rm /var/lib/dpkg/info/folder2ram.prerm
dpkg -P folder2ram
apt-get -f install
fix folders again
reboot
if it is working, re-install the plugin.
Ok, so now I have done what you said. After purging both flashmemory and folder2ram, I checked if they were still installed with apt-cache policy openmediavault-flashmemory folder2ram. Neither of them was.
After a reboot, I installed the flashmemory plugin from web interface, as you told me to, and did a new reboot.
Now the interface is gone. Again.
I then run the same apt-cache policy openmediavault-flashmemory folder2ram code via SSH, and now both flashmemory and folder2ram is installed. I swear I didn't manually installed folder2ram - it was removed the moment before I installed flashmemory.
Any idea what is happening?
Any idea what is happening?
After purging, did you reboot multiple times and the web interface was working each time?
No, I just performed one single reboot... Do you want me to try several?
Can't hurt.
Hey i am also having issues with a missing GUI, tried following some of the steps here but think I might be having a different issue, any chance you would be willing to help me out also?
Is your machine listed on your router’s list of attached devices? Maybe your IP address has changed. Can you ssh into it? Give a little more information and I’m sure somebody will be able to help.
Hi, thanks for the response!
Posted this in another thread of my own but hasn't been seen
Had to change my WebUI port to install Nginx, which worked fine. After a few days of it working fine, I have been unable to access the WebUI from any device, PC, laptop or phone. I ran omv-first aid through SSH(IP is still the same), and changed to port but still no luck. Seems like an error has shown up when I tried changing the port. Pastebin (https://pastebin.com/YCb46S3Z)
My portainer etc is fine and accessible
Cheers!
Need help same issue but nothing posted work
be a bit more verbose about what you see and what you already tried to analyze/ solve it.
Only saying I have the same problem but the solution did not work is expecting g too much from the forum
Sorry my bad, i was a bit affected that nothing i try really worked.
Server specs and config :
OS : openmediavault_5.6.13 ;
Portainer : Active
Main Use : NextCloud - Home Nas ;
Storage config : 1 SSD Samsung 128Gb - > 2 x 120 GB HHD (Mirrored for auto OS Backup)
Main Storage : 3 x1 TB RAID5 ( 1.79TB shared storage for me Phone and Laptop)
Yesterday i got 3 email alert :
email 1 :
The system monitoring needs your attention.
Host: shogo
Date: Wed, 30 Mar 2022 11:49:11
Service: nginx
Event: Does not exist
Description: process is not running
This triggered the monitoring system to: restart"
email 2 :
The system monitoring needs your attention.
Host: shogo
Date: Wed, 30 Mar 2022 11:49:41
Service: nginx
Event: Execution failed
Description: failed to start (exit status 1) -- '/bin/systemctl start nginx': Job for nginx.service failed because the control process exited with error code.See "systemctl status nginx.service" and "journalctl -xe" for details.
This triggered the monitoring system to: alert
email 3 :
The system monitoring needs your attention.
Host: shogo
Date: Wed, 30 Mar 2022 11:49:41
Service: filesystem_srv_dev-disk-by-uuid-47505d39-7dd9-4874-b8ed-10785e4970cb
Event: Does not exist
Description: unable to read filesystem '/srv/dev-disk-by-uuid-47505d39-7dd9-4874-b8ed-10785e4970cb' state
This triggered the monitoring system to: restart
Actions performed :
1. sudo omv-salt deploy run nginx
2.sudo omv-salt deploy run phpfpm
No results
Output form : ls -ld /var/log/nginx
Output form : udo mkdir /var/log/nginx
root@shogo:~# sudo mkdir /var/log/nginx
mkdir: cannot create directory ‘/var/log/nginx’: File exists
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!