Sorry i followed that guide but i can't resolve.
It seems a problem of docker.
Can u help me?
Sorry i followed that guide but i can't resolve.
It seems a problem of docker.
Can u help me?
Hi all, i have the login loop poblem, but i don't know how to clean root disk.
Any suggestion?
thx very much
File system Dim. Usati Dispon. Uso% Montato su
udev 3,8G 0 3,8G 0% /dev
tmpfs 779M 2,7M 777M 1% /run
/dev/sdb2 109G 104G 0 100% /
tmpfs 3,9G 0 3,9G 0% /dev/shm
tmpfs 5,0M 0 5,0M 0% /run/lock
tmpfs 3,9G 0 3,9G 0% /tmp
/dev/sdb1 511M 6,1M 505M 2% /boot/efi
/dev/sda1 3,6T 1,7T 1,9T 48% /srv/dev-disk-by-uuid-29e87996-f75b-4df1-b0d3-2935daec36a2
overlay 109G 104G 0 100% /var/lib/docker/overlay2/469e7cfcc74d3968bd76bfb34cb20d4735c108a4de49b3b4628ad337369f0246/merged
overlay 109G 104G 0 100% /var/lib/docker/overlay2/9191b02a8d4e5007e905a5252224c7704b719e30283ad31fa0c4a4c7ce30561a/merged
overlay 109G 104G 0 100% /var/lib/docker/overlay2/0c85d1ed389d02ba28e480ebdeb1e57f185aa11737e178cdaf38eb36b261c317/merged
Sorry for the delay,
no motherboard has a single NIC.
It is very curious.
It almost seems that some user connected to the electrical system does not comply with the electromagnetic compatibility standards.
Hi all, a curious case: OMV6 machine on q1800 motherboard (J1900 processor), regularly updated.
The server is at my in-laws' house.
Yesterday I noticed, by chance, that the server was losing connection at regular and relatively close intervals (every 3-4 minutes), for 5-10 seconds, then it reconnects.
I ruled out it was an ethernet cable issue, so the cause could be either the modem or the server's network card.
I tend to exclude the modem, because the desktop pc (windows 10) connected to the same network works well and is stable in navigation, so everything leads me to the server's network card.
These are lan specifics on the server:
Interface information enp2s0:
=============================
Settings for enp2s0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: off
master-slave cfg: preferred slave
master-slave status: slave
Port: Twisted Pair
PHYAD: 0
Transceiver: external
MDI-X: Unknown
Supports Wake-on: pumbg
Wake-on: d
Link detected: yes
--------------------------------------------------------------------------------
Driver information enp2s0:
==========================
driver: r8169
version: 6.1.0-0.deb11.5-amd64
firmware-version: rtl8168g-2_0.0.1 02/06/13
expansion-rom-version:
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
I enclose also logfiles.
in the last line of the "messages" log, my (failed) attempt to limit the problem is detected by using the command:
It is very frustrating, I would really appreciate if someone could help me.
Thank u very much.
Hi all,
after a brutal shutdown of my OMV 5 (power failure) , after server (it is a x64 pc) restarting, I can connect via SSH and to the portainer interface but when I try to log into OMV I get the following error:
502 Bad Gateway
nginx
I lunched: sudo omv-salt deploy run phpfpm
with this result (2 errors on phpfpm):
debian:
----------
ID: configure_phpfpm_webgui
Function: file.managed
Name: /etc/php/7.3/fpm/pool.d/openmediavault-webgui.conf
Result: True
Comment: File /etc/php/7.3/fpm/pool.d/openmediavault-webgui.conf is in the correct state
Started: 19:22:33.178909
Duration: 36.61 ms
Changes:
----------
ID: prereq_phpfpm_service_monit
Function: salt.state
Result: True
Comment: States ran successfully. Updating debian.
Started: 19:22:33.217146
Duration: 875.146 ms
Changes:
debian:
----------
ID: configure_monit_collectd_service
Function: file.managed
Name: /etc/monit/conf.d/openmediavault-collectd.conf
Result: True
Comment: File /etc/monit/conf.d/openmediavault-collectd.conf is in the correct state
Started: 19:22:33.783475
Duration: 45.438 ms
Changes:
----------
ID: configure_monit_filesystem_service
Function: file.managed
Name: /etc/monit/conf.d/openmediavault-filesystem.conf
Result: True
Comment: File /etc/monit/conf.d/openmediavault-filesystem.conf is in the correct state
Started: 19:22:33.829068
Duration: 15.366 ms
Changes:
----------
ID: configure_monit_nginx_service
Function: file.managed
Name: /etc/monit/conf.d/openmediavault-nginx.conf
Result: True
Comment: File /etc/monit/conf.d/openmediavault-nginx.conf is in the correct state
Started: 19:22:33.844591
Duration: 13.933 ms
Changes:
----------
ID: configure_monit_omv-engined_service
Function: file.managed
Name: /etc/monit/conf.d/openmediavault-engined.conf
Result: True
Comment: File /etc/monit/conf.d/openmediavault-engined.conf is in the correct state
Started: 19:22:33.858681
Duration: 10.694 ms
Changes:
----------
ID: configure_monit_php-fpm_service
Function: file.managed
Name: /etc/monit/conf.d/openmediavault-phpfpm.conf
Result: True
Comment: File /etc/monit/conf.d/openmediavault-phpfpm.conf is in the correct state
Started: 19:22:33.869533
Duration: 11.108 ms
Changes:
----------
ID: configure_monit_proftpd_service
Function: file.managed
Name: /etc/monit/conf.d/openmediavault-proftpd.conf
Result: True
Comment: File /etc/monit/conf.d/openmediavault-proftpd.conf is in the correct state
Started: 19:22:33.880796
Duration: 12.217 ms
Changes:
----------
ID: configure_monit_rrdcached_service
Function: file.managed
Name: /etc/monit/conf.d/openmediavault-rrdcached.conf
Result: True
Comment: File /etc/monit/conf.d/openmediavault-rrdcached.conf is in the correct state
Started: 19:22:33.893171
Duration: 10.693 ms
Changes:
----------
ID: configure_monit_system_service
Function: file.managed
Name: /etc/monit/conf.d/openmediavault-system.conf
Result: True
Comment: File /etc/monit/conf.d/openmediavault-system.conf is in the correct state
Started: 19:22:33.904018
Duration: 22.177 ms
Changes:
----------
ID: configure_default_monit
Function: file.managed
Name: /etc/default/monit
Result: True
Comment: File /etc/default/monit is in the correct state
Started: 19:22:33.926351
Duration: 2.858 ms
Changes:
----------
ID: divert_default_monit
Function: omv_dpkg.divert_add
Name: /etc/default/monit
Result: True
Comment: Leaving 'local diversion of /etc/default/monit to /etc/default/monit.distrib'
Started: 19:22:33.929933
Duration: 18.796 ms
Changes:
----------
ID: configure_monit_monitrc
Function: file.managed
Name: /etc/monit/monitrc
Result: True
Comment: File /etc/monit/monitrc is in the correct state
Started: 19:22:33.949068
Duration: 24.245 ms
Changes:
----------
ID: divert_monit_monitrc
Function: omv_dpkg.divert_add
Name: /etc/monit/monitrc
Result: True
Comment: Leaving 'local diversion of /etc/monit/monitrc to /etc/monit/monitrc.distrib'
Started: 19:22:33.973471
Duration: 18.774 ms
Changes:
----------
ID: test_monit_config
Function: cmd.run
Name: monit -t
Result: True
Comment: Command "monit -t" run
Started: 19:22:33.994475
Duration: 16.866 ms
Changes:
----------
pid:
21119
retcode:
0
stderr:
stdout:
Control file syntax OK
----------
ID: reload_monit_service
Function: service.running
Name: monit
Result: True
Comment: The service monit is already running
Started: 19:22:34.038207
Duration: 50.374 ms
Changes:
Summary for debian
-------------
Succeeded: 14 (changed=1)
Failed: 0
-------------
Total states run: 14
Total run time: 273.539 ms
----------
ID: test_phpfpm_service_config
Function: cmd.run
Name: php-fpm7.3 --test
Result: True
Comment: Command "php-fpm7.3 --test" run
Started: 19:22:34.093491
Duration: 52.293 ms
Changes:
----------
pid:
21127
retcode:
0
stderr:
[19-May-2022 19:22:34] NOTICE: configuration file /etc/php/7.3/fpm/php-fpm.conf test is successful
stdout:
----------
ID: restart_phpfpm_service
Function: service.running
Name: php7.3-fpm
Result: False
Comment: Job for php7.3-fpm.service failed because the control process exited with error code.
See "systemctl status php7.3-fpm.service" and "journalctl -xe" for details.
Started: 19:22:34.161961
Duration: 123.449 ms
Changes:
----------
ID: monitor_phpfpm_service
Function: module.run
Result: False
Comment: One or more requisite failed: omv.deploy.phpfpm.default.restart_phpfpm_service
Started: 19:22:34.288065
Duration: 0.009 ms
Changes:
Summary for debian
------------
Succeeded: 3 (changed=2)
Failed: 2
I then launched systemctl status php7.3-fpm.service:
● php7.3-fpm.service - The PHP 7.3 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.3-fpm.service; enabled; vendor prese
Active: failed (Result: exit-code) since Thu 2022-05-19 19:33:23 CEST; 20s ag
Docs: man:php-fpm7.3(8)
Process: 21607 ExecStart=/usr/sbin/php-fpm7.3 --nodaemonize --fpm-config /etc/
Main PID: 21607 (code=exited, status=78)
mag 19 19:33:23 OMVHOME systemd[1]: Starting The PHP 7.3 FastCGI Process Manager
mag 19 19:33:23 OMVHOME php-fpm7.3[21607]: [19-May-2022 19:33:23] ERROR: unable
mag 19 19:33:23 OMVHOME php-fpm7.3[21607]: [19-May-2022 19:33:23] ERROR: FPM ini
mag 19 19:33:23 OMVHOME systemd[1]: php7.3-fpm.service: Main process exited, cod
mag 19 19:33:23 OMVHOME systemd[1]: php7.3-fpm.service: Failed with result 'exit
mag 19 19:33:23 OMVHOME systemd[1]: Failed to start The PHP 7.3 FastCGI Process
Then I launched journalctl -xe
--
-- The unit nginx.service has successfully entered the 'dead' state.
mag 19 19:34:54 OMVHOME systemd[1]: Stopped A high performance web server and a
-- Subject: L'unità nginx.service termina la fase di spegnimento
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- L'unità nginx.service ha terminato la fase di spegnimento.
mag 19 19:34:54 OMVHOME monit[2284]: 'nginx' start: '/bin/systemctl start nginx'
mag 19 19:34:54 OMVHOME systemd[1]: Starting A high performance web server and a
-- Subject: L'unità nginx.service inizia la fase di avvio
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- L'unità nginx.service ha iniziato la fase di avvio.
mag 19 19:34:54 OMVHOME systemd[1]: Started A high performance web server and a
-- Subject: L'unità nginx.service termina la fase di avvio
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- L'unità nginx.service ha terminato la fase di avvio.
--
-- La fase di avvio è done.
How can i repair the webpanel?
Thank u very much
Hi all,
i installed OMV 3.x (debian on a core duo machine.
Installed mpd, configured it by this guide (https://www.htpcguides.com/cre…d-music-server-on-debian/), but there's no sound.
It's strange because on a twin machine i installed OMV 4.x (debian 9) and it works perfectly.
The aplay -l command gives this result:
root@OMV:/etc# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC663 Analog [ALC663 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 3: ALC663 Digital [ALC663 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 7: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
Sound card seems to be working.
This is an exctract from my mpd.conf.
# An example of an ALSA output:
#
audio_output {
type "alsa"
name "My ALSA Device"
# device "hw:0,0" # optional
# mixer_type "hardware" # optional
# mixer_device "default" # optional
# mixer_control "PCM" # optional
# mixer_index "0" # optional
Someone could help me?
I was so happy to connect my OMV to my 70s amplier....
Installed on an x86 machine, with debian 8.10 + OMV.
All ok.
Very beautiful openmediavault, i'm spreading it!
Thank u very much
Hi raulfg3,
thank u anyway for the support.
I resolved then, it was a problem related the user wich used to edit the file (sorry it was as you suggest in /var/lib/mldonkey ... wrong writing!).
I was with my user, so rebooted and logged with root.
All ok.
Thank u very much!
Hi everybody, here again for another nightmare fight with mldonkey (god bless them).
Sempron 3000 x86 machine.
Installed debian 8.10
Installed OMV 3.0.95 by your guide Install OMV3 on Debian Jessie
All ok.
Try to install mldonkey with your guide [HOWTO] Install mldonkey-server on OMV to download ed2k links
NIGHTMARE!
mldonkey-server service is active, but in /etc/var/mldonkey there's nothing but only downloads.ini file (with only 3 rows... totally incomplete).
What's wrong?
Thank u very very much for your support. It's very important for me, because if i'll be able to build this machine i will replicate it on more or less 20 P4 and donate them. A beautiful trashwware project!
Sorry for the delay in replying raulfg3, I was trying to prepare an OMV install with mldonkey on a pine64, but it was too instable for me and abandoned the project.
Now i'm trying to install it on a x86 machine, another nightmare.
If u can help me i open another thread.
Thank u very much!
Tried: modified downloads.ini, stopped service then started.
It doesn't work.
Any other suggestion?
Thank u very much!
I hope it will be possible to access, even if i'm forced to uninstall everything and use different OS.
Why OMV doesn't have a mldonkey plugin?
Hi all,
i've installed on OMV (pine64 version) mldonkey using your guide at this address:
[HOWTO] Install mldonkey-server on OMV to download ed2k links
The problem is that it can't connect to core from my desktop pc, i tried everything.
This is my downloads.ini config. It seems all ok. I have no omv firewall rules.
(* list of IP address allowed to connect to the core via telnet/GUI/WEB
for internal command set: list separated by spaces
example for internal command: set allowed_ips "127.0.0.0/8 192.168.1.2"
or for editing the ini-file: list separated by semi-colon
example for ini-file: allowed_ips = [ "127.0.0.0/8"; "192.168.1.2";]
CIDR and range notations are supported: ie use 192.168.0.0/24
or 192.168.0.0-192.168.0.255 for 192.168.0.* *)
allowed_ips = [
"127.0.0.1";
"192.168.1.0/254";
"192.168.3.0/254";]
Alles anzeigen
Someone could help me please?
Thank u very much.