Try putting engined in debug mode and then go to the plugins tab to see what the output of debug mode shows.
sudo monit stop omv-engined
sudo omv-engined -df
Try putting engined in debug mode and then go to the plugins tab to see what the output of debug mode shows.
sudo monit stop omv-engined
sudo omv-engined -df
Sorry for my ignorance , is there a cmd way to find out?
Thanks
Run findmnt /.
Try putting engined in debug mode and then go to the plugins tab to see what the output of debug mode shows.
sudo monit stop omv-engined
sudo omv-engined -df
omv-engined[3258]: Child process forked (pid=3258)
omv-engined[3258]:
omv-engined[3258]: Executing RPC (service=System, method=getInformation, params=null, context={"username":"admin","role":1}) ...
omv-engined[3258]:
omv-engined[3258]: RPC response (service=System, method=getInformation): {"response":{"ts":1649162647,"time":"Tue Apr 5 14:44:07 2022","hostname":"raspberrypi","version":"6.0.20-2 (Shaitan)","cpuModelName":"ARMv7 Processor rev 3 (v7l)","cpuUsage":3.225806451612903,"memTotal":"8282427392","memFree":"6229692416","memUsed":"699789312","memAvailable":"7251095552","memUtilization":"0.12452","kernel":"Linux 5.10.103-v7l+","uptime":3051.63,"loadAverage":{"1min":0.27,"5min":0.47,"15min":0.48},"configDirty":false,"rebootRequired":false,"pkgUpdatesAvailable":false},"error":null}
omv-engined[3258]:
omv-engined[3133]: SIGCHLD received ...
omv-engined[3133]:
omv-engined[3133]: Child (pid=3258) terminated with exit code 0
omv-engined[3133]:
ice=System, method=getInformation): {"response":{"ts":1649162646,"time":"Tue Apr 5 14:44:06 2022","hostname":"raspberrypi","version":"6.0.20-2 (Shaitan)","cpuModelName":"ARMv7 Processor rev 3 (v7l)","cpuUsage":2.272727272727273,"memTotal":"8282427392","memFree":"6230183936","memUsed":"699330560","memAvailable":"7251546112","memUtilization":"0.12446","kernel":"Linux 5.10.103-v7l+","uptime":3050.4,"loadAverage":{"1min":0.29,"5min":0.48,"15min":0.48},"configDirty":false,"rebootRequired":false,"pkgUpdatesAvailable":false},"error":null}
omv-engined[3239]:
omv-engined[3133]: SIGCHLD received ...
omv-engined[3133]:
omv-engined[3133]: Child (pid=3239) terminated with exit code 0
omv-engined[3133]:
omv-engined[3258]: Child process forked (pid=3258)
omv-engined[3258]:
omv-engined[3258]: Executing RPC (service=System, method=getInformation, params=null, context={"username":"admin","role":1}) ...
omv-engined[3258]:
omv-engined[3258]: RPC response (service=System, method=getInformation): {"response":{"ts":1649162647,"time":"Tue Apr 5 14:44:07 2022","hostname":"raspberrypi","version":"6.0.20-2 (Shaitan)","cpuModelName":"ARMv7 Processor rev 3 (v7l)","cpuUsage":3.225806451612903,"memTotal":"8282427392","memFree":"6229692416","memUsed":"699789312","memAvailable":"7251095552","memUtilization":"0.12452","kernel":"Linux 5.10.103-v7l+","uptime":3051.63,"loadAverage":{"1min":0.27,"5min":0.47,"15min":0.48},"configDirty":false,"rebootRequired":false,"pkgUpdatesAvailable":falsomv-engomv-engined[3312]: Child process forked (pid=3312)code 0
Alles anzeigen
Still get error 500 and here is the terminal output.
How do i stop th debug mode?
Thanks
I don't see any output from the plugin list. That could be the problem. Can you try one more time? Hit ctrl-shift-R while looking at the plugin tab and see if the output shows plugins - not system getInformation.
type (doesn't matter if text keeps scrolling)
sudo killall omv-engined
sudo monit start omv-engined
or just reboot from web interface.
Alles anzeigenI don't see any output from the plugin list. That could be the problem. Can you try one more time? Hit ctrl-shift-R while looking at the plugin tab and see if the output shows plugins - not system getInformation.
type (doesn't matter if text keeps scrolling)
sudo killall omv-engined
sudo monit start omv-engined
or just reboot from web interface.
I hope that the information is here
I m using a mac , I have hit ctrl reload
Run findmnt /.
Thanks, here is the result:
root@raspberrypi:/# findmnt /
TARGET SOURCE FSTYPE OPTIONS
/ /dev/mmcblk0p2 ext4 rw,noatime,nodiratime
I hope that the information is here
It is there - 38 plugins. And you still don't see it? This seems like something on the browser side now. Maybe a browser plugin blocking?
Could you please open the browser developer tools by pressing F12 and have a look into the 'Console' tab. If there is an error, they are displayed in red color. Please post them here.
It is there - 38 plugins. And you still don't see it? This seems like something on the browser side now. Maybe a browser plugin blocking?
I see the plugins, when i try to install im getting a 500 error
when i try to install im getting a 500 error
I'm mixing up the two threads. Can you put back in debug mode and try to install a plugin? I would like to see the output from omv-engined when you get that 500 error.
Could you please open the browser developer tools by pressing F12 and have a look into the 'Console' tab. If there is an error, they are displayed in red color. Please post them here.
I m not were how to do that in a mac.
I have borrow 2 computers one running windows 10 another windows 7 I get the same error when trying to install a plugin
I'm mixing up the two threads. Can you put back in debug mode and try to install a plugin? I would like to see the output from omv-engined when you get that 500 error.
Thanks for your help
here is the debug
That was helpful. It is saying that it can't proceed because /var/lib/dpkg/lock is locked. Can you delete that file and then try to install a plugin from the web interface? You might
sudo lsof /var/lib/dpkg/lock
sudo rm /var/lib/dpkg/lock
That was helpful. It is saying that it can't proceed because /var/lib/dpkg/lock is locked. Can you delete that file and then try to install a plugin from the web interface? You might
sudo lsof /var/lib/dpkg/lock
sudo rm /var/lib/dpkg/lock
It work one time, I mean I can install one plugin.
If I try to install one more I get the 500 error
But running
sudo lsof /var/lib/dpkg/lock[
sudo rm /var/lib/dpkg/lock
Then I can again install a plugin.
Has it been locked again or didn't you follow #9 (as indicated in #10)?
Edit:
I see, you installed a plugin from the cli and that might have made it lock again
ls -ahl /var/lib/dpkg/ lock before you delete it again.
install or remove a plugin fro mthe cli
ls -ahl /var/lib/dpkg/
this will rule out OMV as the reason. (Not that it helps you at the moment, but narrows down the source of error)
Has it been locked again od didn't you follow #9 (as indicated in #10)?
If I run your cmd it gets locked I think when I run sudo dpkg --configure -a
Without that I can install one plugin. then run again
sudo lsof /var/lib/dpkg/lock[
sudo rm /var/lib/dpkg/lock
Then I can install one more
this will rule out OMV as the reason.
When he deletes the lock and installs the plugin, omv is just running apt-get install. The lock file is being recreated. OMV is just check for a lock on that file. I don't know why someone thing is keeping a lock on the file.
When he deletes the lock and installs the plugin, omv is just running apt-get install. The lock file is being recreated. OMV is just check for a lock on that file. I don't know why someone thing is keeping a lock on the file.
But from terminal i can install without problem several plugins in a row
But from terminal i can install without problem several plugins in a row
I thought you had to delete the lock file after each install?
I thought you had to delete the lock file after each install?
Sorry for the misunderstanding.
From terminal works all time.
Its when i run via the web interface plugins that I have to delete the lock file after each install.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!