Jump to content

juan11perez

Members
  • Posts

    192
  • Joined

  • Last visited

Posts posted by juan11perez

  1. On 1/12/2021 at 9:01 PM, pm1961 said:

    Hi,

     

    After an update of a working instance of Zoneminder, I have the problem of;

     

    Unable to connect to ZM db.SQLSTATE[HY000] [2002] No such file or directory

     

    On inspection of the log (bottom), it references the MariaDB.

     

    When I use mc to try and navigate to the floder/files referred too..... they don't exist.... presumably because the "kill" at the end deletes them?

     

    After much frustration, I installed a fresh Zoneminder on my other unRaid server. This server runs as a NAS with no other dockers........ and that works fine!

     

    So........... if it's an interaction between Zoneminder and my MariaDB, is there a workaround? I only have MariaDB because of my Nextcloud instance, and they work fine together.

     

    This server is my high core/high memory VM and docker server so, although it works, I dont want to leave Zoneminder on my NAS server.

     

    Having read through the forum, I've tried deleting templates for a fresh install from CA...... I've tried deleting log files.... but they didn't exist.... presumably because it's never done anything............

     

    I noticed from comparing the Appdata folders that the non-working instance has an extra directory "opencv". My working version doesn't have this even though it was installed after the broken one???

     

    Any help gratefully received,

     

    ATB,

     

    Paul

     

     

    Starting services...
    * Starting Apache httpd web server apache2
    *

    * Starting MariaDB database server mysqld
    Jan 12 15:23:43 70771cb7af9e web_php[657]: FAT [Failed db connection to ]
    ...fail!
    DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
    DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
    DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
    Jan 12 15:24:12 70771cb7af9e zmupdate[1092]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:]
    Can't call method "prepare_cached" on an undefined value at /usr/share/perl5/ZoneMinder/Config.pm line 96.
    BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 147.
    Compilation failed in require at /usr/bin/zmupdate.pl line 73.
    BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 73.
    Jan 12 15:24:12 70771cb7af9e zmupdate[1092]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:]
    DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
    DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
    Jan 12 15:24:12 70771cb7af9e zmupdate[1094]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:]
    DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
    Can't call method "prepare_cached" on an undefined value at /usr/share/perl5/ZoneMinder/Config.pm line 96.
    BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 147.
    Compilation failed in require at /usr/bin/zmupdate.pl line 73.
    BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 73.
    Jan 12 15:24:12 70771cb7af9e zmupdate[1094]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:]
    Starting ZoneMinder:
    DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
    DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
    Jan 12 15:24:12 70771cb7af9e zmpkg[1104]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:]
    DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110.
    Can't call method "prepare_cached" on an undefined value at /usr/share/perl5/ZoneMinder/Config.pm line 96.
    BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 147.
    Compilation failed in require at /usr/share/perl5/ZoneMinder.pm line 33.
    BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder.pm line 33.
    Compilation failed in require at /usr/bin/zmpkg.pl line 34.
    BEGIN failed--compilation aborted at /usr/bin/zmpkg.pl line 34.
    Jan 12 15:24:12 70771cb7af9e zmpkg[1104]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:]
    ZoneMinder failed to start

    *** /etc/my_init.d/40_firstrun.sh failed with status 255

    *** Killing all processes...
    Jan 12 15:24:12 70771cb7af9e syslog-ng[38]: syslog-ng shutting down; version='3.25.1'

    good day, I found a way to get zm back with this post

    https://forums.zoneminder.com/viewtopic.php?t=29602

    however, it doesn't say what's creating it.

  2. Good day. First thank you for producing this tool.

    I had been experiencing significant system lagging last week and afer changing sata cables, usb stick, inspecting docker by docker etc I finally came across this tool and tested.

     

    These are drive 1 tests over the last few days with services (docker,vms) online. it's all over the place.

     

    benchmark-speeds.thumb.jpeg.9d57eb770b58df4415917af7d51ef093.jpeg

     

    These are for all drives with all services off. Seems to be ok, or at least not worse than the rest.

     

    1968519001_benchmark-speeds(1).thumb.jpeg.025123bc7ebb02f132591edb5098743f.jpeg

     

     

    Any advise welcome. Thank you

  3. Good day. Over the last week unraid has become unusually slow. 

    Started aproximately 6 days ago, where the system would become unresponsive when trying to stop dockers. Even after stoping the docker service, some containers would continue to appear to be running and when attempting to stop them via cli it would report they're already being stopped.

     

    After a restart, the system runs fine for aproximately 12 hours and then the same pattern starts. Looking at glances the load increases to the below numbers when histofically (about 1.5 year) they've all hovered around 4..

     

    LOAD 24-core

    1 min: 17.03

    5 min:18.85

    15 min:19.64

     

    I havent noticed anything unusual hardware-wise, but i must obviously be missing something.

     

    See attached logs.

     

    Any guidance is much appreciated.

     

    Thank you

     

     

     

    tower-diagnostics-20210306-1956.zip

  4. @JorgeB

    Short note to update and again thank you for your advise. 

     

    Adding "nvme_core.default_ps_max_latency_us=0" to syslinux did not resolve the issue. The drive kept disconnecting. 

     

    I replaced it with a Samsung 970plus and that stopped the problem. Sever has now been running for over 10 days with no issues.

     

    Not sure if this means the Adata drive failed, but if it did it's quite disappointing as it's only 2 years old and the internet is full of praises for this product.

     

    • Like 1
  5. Good day, 

    About 4 days ago docker crashed. All dockers reside in /mnt/cache. Cache being ADATA_SX8200PNP_2J3420080645 (nvme0n1)

    When i checked in the main tab, the drive had disappeared. All else was fine. 
    i restarted the server a couple of times, with no luck. I presumed a faulty drive; so I removed it and installed another nvme drive in the same pci slot and the new drive showed up. So sort of confirmed my suspicion. Nevertheless I reinstalled the presumed failed drive in its old location restarted and it appeared again. 

     

    Server run fine last 4 days. This morning docker was again dead. I pulled the attached log and restarted unraid. All is working again.

    Apparently the drive disconnected at 1:48am. 

     

    Should I assume the drive has had it? It's 2 years old.

     

    Thank you 

    syslog.txt

×
×
  • Create New...