Sporadisch auftretende Fehlermeldung nach Update

Hilfe zu OTRS Problemen aller Art
Post Reply
vinzenzb
Znuny newbie
Posts: 3
Joined: 03 Mar 2022, 11:49
Znuny Version: 6.0.39
Real Name: Vinzenz

Sporadisch auftretende Fehlermeldung nach Update

Post by vinzenzb »

Hallo zusammen,

ich hab eine OTRS Installation von 6.0.8 auf znuny 6.0.39 geupdatet und habe jetzt zweimal in 3 Wochen folgende Fehlermeldungen im Systemprotokoll:

Code: Select all

Tue Jun 14 11:41:23 2022 (Europe/Berlin)	error	OTRS-CGI-78	Can't locate Kernel/Modules/undefined.pm in @INC (you may need to install the Kernel::Modules::undefined module) (@INC contains: /opt/otrs/Custom /opt/otrs/Kernel/cpan-lib /opt/otrs/ /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl . /etc/apache2) at /opt/otrs/Kernel/System/Main.pm line 86.
Tue Jun 14 11:41:23 2022 (Europe/Berlin)	error	OTRS-CGI-78	Can't locate Kernel/Modules/undefined.pm in @INC (you may need to install the Kernel::Modules::undefined module) (@INC contains: /opt/otrs/Custom /opt/otrs/Kernel/cpan-lib /opt/otrs/ /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl . /etc/apache2) at /opt/otrs/Kernel/System/Main.pm line 86.
Tue Jun 14 11:40:35 2022 (Europe/Berlin)	error	OTRS-otrs.Daemon.pl - Daemon Kernel::System::Daemon::DaemonModules::SystemConfigurationSyncManager-78	Can't connect to MySQL server on '127.0.0.1' (111)
Tue Jun 14 11:40:34 2022 (Europe/Berlin)	error	OTRS-CGI-78	Can't connect to MySQL server on '127.0.0.1' (111)
Tue Jun 14 11:40:34 2022 (Europe/Berlin)	error	OTRS-CGI-78	Can't connect to MySQL server on '127.0.0.1' (111)
Tue Jun 14 11:40:34 2022 (Europe/Berlin)	error	OTRS-CGI-78	Can't connect to MySQL server on '127.0.0.1' (111)
Tue Jun 14 11:40:34 2022 (Europe/Berlin)	error	OTRS-CGI-78	Can't connect to MySQL server on '127.0.0.1' (111)
Tue Jun 14 11:40:34 2022 (Europe/Berlin)	error	OTRS-CGI-78	Need TicketID!
Tue Jun 14 11:40:34 2022 (Europe/Berlin)	error	OTRS-CGI-78	Need ArticleID!
Tue Jun 14 11:40:34 2022 (Europe/Berlin)	error	OTRS-CGI-78	Need TicketID!
Alle Anfragen die die Agenten zu der Zeit tätigen sehen dann die Fehlermeldung "Can't connect to MySQL server on '127.0.0.1' (111). Bitte kontaktieren Sie den Administrator". Die Problematik tritt dann solange auf, bis ich den apache2 einmal neustarte. Im error.log vom apache2 sind zu der gleichen Zeit folgende Einträge zu finden:

Code: Select all

[Tue Jun 14 11:40:34 2022] -e: DBI connect('database=otrs;host=127.0.0.1','otrs',...) failed: Can't connect to MySQL server on '127.0.0.1' (111) at /opt/otrs/Kernel/System/DB.pm line 209.
ERROR: OTRS-CGI-78 Perl: 5.22.1 OS: linux Time: Tue Jun 14 11:40:34 2022

 Message: Can't connect to MySQL server on '127.0.0.1' (111)

 RemoteAddress: [ip]
 RequestURI: /otrs/index.pl?Action=AgentTicketZoom;TicketID=26074

 Traceback (19784):
   Module: Kernel::System::DB::Do Line: 468
   Module: Kernel::System::AuthSession::DB::DESTROY Line: 602
   Module: (eval) Line: 581
   Module: Kernel::System::ObjectManager::ObjectsDiscard Line: 581
   Module: Kernel::System::ObjectManager::DESTROY Line: 643
   Module: (eval) (v1.99) Line: 207
   Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler (v1.99) Line: 207
   Module: (eval) (v1.99) Line: 207
   Module: ModPerl::RegistryCooker::run (v1.99) Line: 207
   Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 173
   Module: ModPerl::Registry::handler (v1.99) Line: 32

SV = PV(0x55ec0e5e6870) at 0x55ec0e79cfc8
  REFCNT = 2
  FLAGS = ()
  PV = 0
SV = PV(0x7f1fa8763b00) at 0x7f1fa88e2358
  REFCNT = 2
  FLAGS = ()
  PV = 0
... weitere SV = PV Protokolleinträge ...
SV = PV(0x55ec0e5e6870) at 0x55ec0e79cfc8
  REFCNT = 2
  FLAGS = ()
  PV = 0
[Tue Jun 14 11:40:48.058222 2022] [core:notice] [pid 6375] AH00051: child pid 19866 exit signal Segmentation fault (11), possible coredump in /etc/apache2
SV = PV(0x55ec0e5e6870) at 0x55ec10abb508
  REFCNT = 2
  FLAGS = ()
  PV = 0
... weitere SV = PV Protokolleinträge ...
SV = PV(0x55ec0e5e6870) at 0x55ec10abb508
  REFCNT = 2
  FLAGS = ()
  PV = 0
ERROR: OTRS-CGI-78 Perl: 5.22.1 OS: linux Time: Tue Jun 14 11:41:23 2022

 Message: Can't locate Kernel/Modules/undefined.pm in @INC (you may need to install the Kernel::Modules::undefined module) (@INC contains: /opt/otrs/Custom /opt/otrs/Kernel/cpan-lib /opt/otrs/ /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl . /etc/apache2) at /opt/otrs/Kernel/System/Main.pm line 86.


 RemoteAddress: [ip]
 RequestURI: /otrs/index.pl

 Traceback (19811):
   Module: Kernel::System::Web::InterfaceAgent::Run Line: 217
   Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler Line: 39
   Module: (eval) (v1.99) Line: 207
   Module: ModPerl::RegistryCooker::run (v1.99) Line: 207
   Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 173
   Module: ModPerl::Registry::handler (v1.99) Line: 32

ERROR: OTRS-CGI-78 Perl: 5.22.1 OS: linux Time: Tue Jun 14 11:41:23 2022

 Message: Can't locate Kernel/Modules/undefined.pm in @INC (you may need to install the Kernel::Modules::undefined module) (@INC contains: /opt/otrs/Custom /opt/otrs/Kernel/cpan-lib /opt/otrs/ /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl . /etc/apache2) at /opt/otrs/Kernel/System/Main.pm line 86.


 RemoteAddress: [ip]
 RequestURI: /otrs/index.pl

 Traceback (19797):
   Module: Kernel::System::Web::InterfaceAgent::Run Line: 217
   Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler Line: 39
   Module: (eval) (v1.99) Line: 207
   Module: ModPerl::RegistryCooker::run (v1.99) Line: 207
   Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 173
   Module: ModPerl::Registry::handler (v1.99) Line: 32

SV = PV(0x55ec0e5e6870) at 0x55ec10abb508
  REFCNT = 2
  FLAGS = ()
  PV = 0
... weitere SV = PV Protokolleinträge ...
SV = PV(0x55ec0e5e6870) at 0x55ec10abb508
  REFCNT = 2
  FLAGS = ()
  PV = 0
[Tue Jun 14 11:42:06.988166 2022] [mpm_prefork:notice] [pid 6375] AH00169: caught SIGTERM, shutting down
[Tue Jun 14 11:42:08.172735 2022] [mpm_prefork:notice] [pid 20305] AH00163: Apache/2.4.18 (Ubuntu) mod_auth_gssapi/1.3.3 mod_auth_kerb/5.4 mod_perl/2.0.9 Perl/v5.22.1 configured -- resuming normal operations
[Tue Jun 14 11:42:08.172859 2022] [core:notice] [pid 20305] AH00094: Command line: '/usr/sbin/apache2'
[Tue Jun 14 11:53:22 2022] -e: Use of uninitialized value in pattern match (m//) at /opt/otrs/Kernel/Modules/AgentTicketCompose.pm line 1636.
Das mysql error.log enhält folgende Einträge (hier ist die Zeit um zwei Stunden verschoben). Vor 09:39 (11:39 Uhr) ist nichts im Protokoll:

Code: Select all

2022-06-14T09:39:10.078104Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2022-06-14T09:39:10.079407Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2022-06-14T09:39:10.266369Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2022-06-14T09:39:10.283868Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.22-0ubuntu0.16.04.1) starting as process 19957 ...
2022-06-14T09:39:10.495426Z 0 [Note] InnoDB: PUNCH HOLE support available
2022-06-14T09:39:10.495458Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-06-14T09:39:10.495464Z 0 [Note] InnoDB: Uses event mutexes
2022-06-14T09:39:10.495469Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-06-14T09:39:10.495474Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2022-06-14T09:39:10.495479Z 0 [Note] InnoDB: Using Linux native AIO
2022-06-14T09:39:10.499705Z 0 [Note] InnoDB: Number of pools: 1
2022-06-14T09:39:10.533169Z 0 [Note] InnoDB: Using CPU crc32 instructions
2022-06-14T09:39:10.562371Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2022-06-14T09:39:10.609651Z 0 [Note] InnoDB: Completed initialization of buffer pool
2022-06-14T09:39:10.615617Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-06-14T09:39:10.678999Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2022-06-14T09:39:10.781074Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 114412374541
2022-06-14T09:39:10.781215Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 114412399696
2022-06-14T09:39:10.840638Z 0 [Note] InnoDB: Database was not shutdown normally!
2022-06-14T09:39:10.840656Z 0 [Note] InnoDB: Starting crash recovery.
2022-06-14T09:39:13.301865Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
2022-06-14T09:39:17.804330Z 0 [Note] InnoDB: Apply batch completed
2022-06-14T09:39:44.999903Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-06-14T09:39:45.406888Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-06-14T09:39:47.328600Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-06-14T09:39:49.053409Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-06-14T09:39:52.192265Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2022-06-14T09:39:52.239455Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2022-06-14T09:39:52.692236Z 0 [Note] InnoDB: Waiting for purge to start
2022-06-14T09:39:52.742363Z 0 [Note] InnoDB: Waiting for purge to start
2022-06-14T09:39:52.792483Z 0 [Note] InnoDB: Waiting for purge to start
2022-06-14T09:39:52.842560Z 0 [Note] InnoDB: Waiting for purge to start
2022-06-14T09:39:52.892681Z 0 [Note] InnoDB: Waiting for purge to start
2022-06-14T09:39:52.942808Z 0 [Note] InnoDB: Waiting for purge to start
2022-06-14T09:39:52.992945Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 42377ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2022-06-14T09:39:53.000519Z 0 [Note] InnoDB: 5.7.22 started; log sequence number 114412399696
2022-06-14T09:39:53.026860Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-06-14T09:39:53.450749Z 0 [Note] Plugin 'FEDERATED' is disabled.
2022-06-14T09:39:55.291537Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2022-06-14T09:39:55.309442Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2022-06-14T09:39:55.309514Z 0 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
2022-06-14T09:39:55.325946Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2022-06-14T09:40:35.891300Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2022-06-14T09:40:35.891415Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2022-06-14T09:40:36.071551Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2022-06-14T09:40:36.075387Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.22-0ubuntu0.16.04.1) starting as process 20093 ...
2022-06-14T09:40:36.116852Z 0 [Note] InnoDB: PUNCH HOLE support available
2022-06-14T09:40:36.116882Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-06-14T09:40:36.116887Z 0 [Note] InnoDB: Uses event mutexes
2022-06-14T09:40:36.116891Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-06-14T09:40:36.116895Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2022-06-14T09:40:36.116900Z 0 [Note] InnoDB: Using Linux native AIO
2022-06-14T09:40:36.119909Z 0 [Note] InnoDB: Number of pools: 1
2022-06-14T09:40:36.122852Z 0 [Note] InnoDB: Using CPU crc32 instructions
2022-06-14T09:40:36.125556Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2022-06-14T09:40:36.135601Z 0 [Note] InnoDB: Completed initialization of buffer pool
2022-06-14T09:40:36.139943Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-06-14T09:40:36.167114Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2022-06-14T09:40:36.174698Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 114412400247
2022-06-14T09:40:36.174716Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 114412400256
2022-06-14T09:40:36.174722Z 0 [Note] InnoDB: Database was not shutdown normally!
2022-06-14T09:40:36.174727Z 0 [Note] InnoDB: Starting crash recovery.
2022-06-14T09:40:36.810397Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-06-14T09:40:36.810430Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-06-14T09:40:36.810473Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-06-14T09:40:36.851912Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-06-14T09:40:36.852894Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2022-06-14T09:40:36.852910Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2022-06-14T09:40:36.853267Z 0 [Note] InnoDB: Waiting for purge to start
2022-06-14T09:40:36.903782Z 0 [Note] InnoDB: 5.7.22 started; log sequence number 114412400256
2022-06-14T09:40:36.903975Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-06-14T09:40:36.904081Z 0 [Note] Plugin 'FEDERATED' is disabled.
2022-06-14T09:40:36.924463Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2022-06-14T09:40:36.924480Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2022-06-14T09:40:36.924491Z 0 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
2022-06-14T09:40:36.924527Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2022-06-14T09:40:37.071807Z 0 [Note] Event Scheduler: Loaded 0 events
2022-06-14T09:40:37.072892Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.22-0ubuntu0.16.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
2022-06-14T09:40:37.843637Z 5 [Note] Access denied for user 'root'@'localhost' (using password: NO)
2022-06-14T09:40:39.497854Z 0 [Note] InnoDB: Buffer pool(s) load completed at 220614 11:40:39
Hat jemand vielleicht eine Idee was zu den Fehlern führen kann? Habe ich beim Update irgendwelche Datenbankeinstellungen übersehen?

Gruß
root
Administrator
Posts: 3934
Joined: 18 Dec 2007, 12:23
Znuny Version: Znuny and Znuny LTS
Real Name: Roy Kaldung
Company: Znuny
Contact:

Re: Sporadisch auftretende Fehlermeldung nach Update

Post by root »

Hallo,

ich würde mal in der Ausgabe von dmesg -T schauen ob zu dem Zeitpunkt der Kernel einen Prozess, hier wohl die Datenbank, wegen Speichermangel gekillt hat. Da steht denn beispielweise sowas drin:

Code: Select all

Out of memory: Killed process 21000, UID 48, (httpd).
mysqld invoked oom-killer: gfp_mask=0x201d2, order=0, oomkilladj=0
- Roy
Znuny and Znuny LTS running on CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO

Use a test system - always.

Do you need professional services? Check out https://www.znuny.com/

Do you want to contribute or want to know where it goes ?
vinzenzb
Znuny newbie
Posts: 3
Joined: 03 Mar 2022, 11:49
Znuny Version: 6.0.39
Real Name: Vinzenz

Re: Sporadisch auftretende Fehlermeldung nach Update

Post by vinzenzb »

Hallo Roy,

genau diese Meldungen habe ich wenn ich dmesg -T ausführe:

Code: Select all

[Di Jun 14 10:57:34 2022] Out of memory: Kill process 19728 (/usr/sbin/apach) score 14 or sacrifice child
[Di Jun 14 10:57:34 2022] Killed process 19728 (/usr/sbin/apach) total-vm:367848kB, anon-rss:82572kB, file-rss:48kB
[Di Jun 14 10:57:39 2022] /opt/otrs/bin/c invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=0
[Di Jun 14 10:57:39 2022] /opt/otrs/bin/c cpuset=/ mems_allowed=0
...
[Di Jun 14 10:57:39 2022] Out of memory: Kill process 19736 (/opt/otrs/bin/c) score 14 or sacrifice child
[Di Jun 14 10:57:39 2022] Killed process 19736 (/opt/otrs/bin/c) total-vm:365140kB, anon-rss:71896kB, file-rss:0kB
[Di Jun 14 10:57:42 2022] /opt/otrs/bin/c invoked oom-killer: gfp_mask=0x24280ca, order=0, oom_score_adj=0
[Di Jun 14 10:57:42 2022] /opt/otrs/bin/c cpuset=/ mems_allowed=0
[Di Jun 14 10:57:42 2022] CPU: 0 PID: 19789 Comm: /opt/otrs/bin/c Not tainted 4.4.0-130-generic #156-Ubuntu
...
[Di Jun 14 10:57:42 2022] Out of memory: Kill process 19749 (/opt/otrs/bin/c) score 14 or sacrifice child
[Di Jun 14 10:57:42 2022] Killed process 19749 (/opt/otrs/bin/c) total-vm:359336kB, anon-rss:91448kB, file-rss:0kB
[Di Jun 14 10:57:46 2022] /opt/otrs/bin/c invoked oom-killer: gfp_mask=0x2420848, order=0, oom_score_adj=0
[Di Jun 14 10:57:46 2022] /opt/otrs/bin/c cpuset=/ mems_allowed=0
...
[Di Jun 14 10:57:46 2022] Out of memory: Kill process 19750 (/usr/sbin/apach) score 13 or sacrifice child
[Di Jun 14 10:57:46 2022] Killed process 19750 (/usr/sbin/apach) total-vm:358540kB, anon-rss:71036kB, file-rss:0kB
[Di Jun 14 10:57:50 2022] perl invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=0
[Di Jun 14 10:57:50 2022] perl cpuset=/ mems_allowed=0
...
[Di Jun 14 10:57:50 2022] Out of memory: Kill process 19752 (/usr/sbin/apach) score 13 or sacrifice child
[Di Jun 14 10:57:50 2022] Killed process 19752 (/usr/sbin/apach) total-vm:358176kB, anon-rss:102076kB, file-rss:0kB
[Di Jun 14 10:57:50 2022] systemd-journald[380]: /dev/kmsg buffer overrun, some messages lost.
[Di Jun 14 10:57:59 2022] mysqld invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=0
[Di Jun 14 10:57:59 2022] mysqld cpuset=/ mems_allowed=0
...
[Di Jun 14 10:57:59 2022] Out of memory: Kill process 19957 (mysqld) score 14 or sacrifice child
[Di Jun 14 10:57:59 2022] Killed process 19957 (mysqld) total-vm:1344944kB, anon-rss:64728kB, file-rss:0kB
[Di Jun 14 10:58:07 2022] perl invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=0
[Di Jun 14 10:58:07 2022] perl cpuset=/ mems_allowed=0
[Di Jun 14 10:58:07 2022] CPU: 2 PID: 719 Comm: perl Not tainted 4.4.0-130-generic #156-Ubuntu
...
[Di Jun 14 10:58:07 2022] Out of memory: Kill process 19755 (/usr/sbin/apach) score 13 or sacrifice child
[Di Jun 14 10:58:07 2022] Killed process 19755 (/usr/sbin/apach) total-vm:358176kB, anon-rss:103100kB, file-rss:0kB
Kann ich da irgendwas machen, dass der Kernel diese Prozesse nicht killt, oder einfach der VM mehr Arbeitsspeicher geben?
Johannes
Moderator
Posts: 391
Joined: 30 Jan 2008, 02:26
Znuny Version: All of them ^^
Real Name: Hannes
Company: Znuny|OTTERHUB

Re: Sporadisch auftretende Fehlermeldung nach Update

Post by Johannes »

Hi,

generell ist mehr RAM mehr gut. Mit dem Update selbst hat das in meinen Augen nicht viel zu tun. Znuny / OTRS CE braucht nicht wirklich mehr RAM nach einem Update .
Wie viel RAM hat denn die Maschine? Bzw laufen da noch andere Applikationen außer dem Ticket System, die da ggf. Speicher fressen?

Gruß
Johannes
vinzenzb
Znuny newbie
Posts: 3
Joined: 03 Mar 2022, 11:49
Znuny Version: 6.0.39
Real Name: Vinzenz

Re: Sporadisch auftretende Fehlermeldung nach Update

Post by vinzenzb »

Aktuell hat die VM 8GB RAM.
Eigentlich müsste da nur das laufen, was für das Ticketsystem benötigt wird.

Code: Select all

ps -eo pid,ppid,cmd,%mem,%cpu --sort=-%mem |head -n 30
  PID  PPID CMD                         %MEM %CPU
20093     1 /usr/sbin/mysqld             7.2  0.7
29807 20305 /usr/sbin/apache2 -k start   2.7  0.2
30284 20305 /usr/sbin/apache2 -k start   2.4  0.2
30355 20305 /usr/sbin/apache2 -k start   2.2  0.2
31075 20305 /usr/sbin/apache2 -k start   2.0  0.3
31188 20305 /usr/sbin/apache2 -k start   1.9  0.3
31110 20305 /usr/sbin/apache2 -k start   1.9  0.2
31199 20305 /usr/sbin/apache2 -k start   1.8  0.2
31287 20305 /usr/sbin/apache2 -k start   1.8  0.4
31269 20305 /usr/sbin/apache2 -k start   1.7  0.3
31267 20305 /usr/sbin/apache2 -k start   1.7  0.3
30469   719 perl bin/otrs.Daemon.pl sta  0.5  0.0
30470   719 perl bin/otrs.Daemon.pl sta  0.4  0.0
30462   719 perl bin/otrs.Daemon.pl sta  0.4  0.0
20305     1 /usr/sbin/apache2 -k start   0.4  0.0
30476   719 perl bin/otrs.Daemon.pl sta  0.3  0.1
30475   719 perl bin/otrs.Daemon.pl sta  0.3  0.1
  914     1 /usr/lib/snapd/snapd         0.1  0.0
  380     1 /lib/systemd/systemd-journa  0.1  0.0
22087  1008 sshd: [USER] [priv]       0.0  0.0
22157 22156 -su                          0.0  0.0
22142 22141 -bash                        0.0  0.0
    1     0 /sbin/init                   0.0  0.0
22141 22087 sshd: [USER]@pts/1        0.0  0.0
  630     1 /usr/bin/vmtoolsd            0.0  0.0
 1033     1 /sbin/iscsid                 0.0  0.0
22156 22142 su -                         0.0  0.0
31336 22157 ps -eo pid,ppid,cmd,%mem,%c  0.0  0.0
  908     1 /usr/lib/accountsservice/ac  0.0  0.0
Beim prüfen des bereitgestellten RAM hab ich gesehen das die VM seit 3 Monaten auf einem Snapshot lief. Das war bestimmt nicht gerade performancesteigernd :) .
hkais
Znuny expert
Posts: 280
Joined: 16 Apr 2016, 08:55
Znuny Version: see in post
Real Name: Hans
Contact:

Re: Sporadisch auftretende Fehlermeldung nach Update

Post by hkais »

hier gibt es 3 Lösungswege:

1. Problem mit Hardware (RAM) erschlagen
2. Problem eingrenzen, warum mehr RAM benötigt wird
2.1 die Anzahl der Apache Prozesse begrenzen und deren Lebenszeit "verkürzen" damit der Speicher wieder freigegeben wird
2.2 die MySQL/Maria genauer unter die Lupe nehmen, warum diese plötzlich speicherhungrig wird (slow sql müsste schnell helfen)

welches MPM für apache modul verwendest Du? Und welche Ubuntu distri? (18.04?)
Elected 2022-06 as an IT Governance Portal Expert. The portal for Znuny, OTRS and OTOBO users
Post Reply