I am getting this error in the Icinga startup -
/pkgs/icinga/1.13.3.rhas5/bin/icinga /my-config/dit-icinga-app-master/config/icinga.cfg
Icinga 1.13.3
Copyright (c) 2009-2015 Icinga Development Team (http://www.icinga.org)
Copyright (c) 2009-2013 Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 07-15-2015
License: GPL
Icinga 1.13.3 starting... (PID=30807)
Local time is Fri Feb 05 16:45:17 EST 2016
idomod: IDOMOD 1.13.3 (07-15-2015) Copyright(c) 2005-2008 Ethan Galstad, Copyright(c) 2009-2015 Icinga Development Team (https://www.icinga.org)
idomod: Successfully connected to data sink. 0 queued items to flush.
Memory fault(coredump)
Log file does not reveal much
icinga.log
[1454708717] Icinga 1.13.3 starting... (PID=30807)
[1454708717] Local time is Fri Feb 05 16:45:17 EST 2016
[1454708717] LOG VERSION: 2.0
[1454708717] idomod: IDOMOD 1.13.3 (07-15-2015) Copyright(c) 2005-2008 Ethan Galstad, Copyright(c) 2009-2015 Icinga Development Team (https://www.icinga.org)
[1454708717] idomod: Successfully connected to data sink. 0 queued items to flush.
[1454708717] Event broker module 'IDOMOD' version '1.13.3' from '/pkgs/icinga_idoutils_libdbi_mysql/1.13.3/lib64/icinga/idomod.so' initialized successfully.
[1454708718] Event loop started...
icinga.log (END)
Icinga pre-flight check looks OK, so there is no issue with any of the configuration files.
Also, MySQL database is running on the node and I do see some data being inserted to it also in ido2db.debug logs.
Wondering where can I get more logs? Anybody has any leads? Appreciate your help.
Related
We are using Nagios XI with Nagios Core 4.4.5. We have updated clients to nrpe 4.0.3 agent. We get "Remote does not support Version 3 Packets" messages in the server log. How to solve this, shouldn't nrpe 4.0.3 support version 3 packets by default. Is there something missing in the configuration? We know that requests can be configured to use version 2, only, but using the newest version is better, isn't it?
EDIT:
nagios-server:~$ /usr/local/nagios/bin/nagios -h
Nagios Core 4.4.5
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2019-08-20
License: GPL
nagios-server:~$ cat /usr/local/nagiosxi/var/xiversion
full=5.6.7
major=5
minor=6.7
releasedate=2019-09-26
release=5607
Most likely you updated the NRPE client but did not update the plugins in the agent machine
Run these commands to check some plugins versions (nrpe, http, ping):
/usr/lib/nagios/plugins/check_nrpe --version
/usr/lib/nagios/plugins/check_http --version
/usr/lib/nagios/plugins/check_ping --version
Also run this command to check the nrpe daemon version:
/usr/sbin/nrpe-ng --version
Most likely you would get reported version below 3 so you will need to update the plugins.
I have an licensed Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Version 19.7.0.0.0. Furthermore I have another Oracle DB in a docker container that has been created as described in DockerFiles, whihc is 18.4.0 xe.
I want to transfer the schema/data from 19c to 18.4xe. I have used the following command to export the data from 19c:
expdp system/pwd#db DIRECTORY=export_dir_local SCHEMAS=MYSCHEMA CONSISTENT=yes EXCLUDE=statistics COMPRESSION=all VERSION=18.1.0 DUMPFILE=mydump.dmp LOGFILE=mydump.log
and then in the docker I import it by using
impdp system/pwd#localhost/xepdb1 directory=DUMP_DIR dumpfile=mydump.dmp exclude=STATISTICS LOGFILE=mydump.log
However when I run the command I receive the following error:
Import: Release 18.0.0.0.0 - Production on Wed Mar 3 19:15:39 2021
Version 18.4.0.0.0
Copyright (c) 1982, 2018, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 18c Express Edition Release 18.0.0.0.0 - Production
ORA-39002: invalid operation
while the log contains:
;;;
Import: Release 18.0.0.0.0 - Production on Wed Mar 3 19:15:39 2021
Version 18.4.0.0.0
Copyright (c) 1982, 2018, Oracle and/or its affiliates. All rights reserved.
;;;
Connected to: Oracle Database 18c Express Edition Release 18.0.0.0.0 - Production
Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Job "SYSTEM"."SYS_IMPORT_FULL_01" successfully completed at Wed Mar 3 19:15:46 2021 elapsed 0 00:00:04
Job "SYSTEM"."SYS_IMPORT_FULL_01" successfully completed at Wed Mar 3 19:15:46 2021 elapsed 0 00:00:04
I have tried also to export it with COMPRESSION=NONO with the same error and by changing the version VERSION=18 or VERSION=18.4.0
but I receive the error:
Connected to: Oracle Database 18c Express Edition Release 18.0.0.0.0 - Production
ORA-39002: invalid operation
ORA-39358: Export dump file version 18.4.0 not compatible with target version 18.1.0.0.0
Furthermore in "show parameter compatible" I receive
NAME TYPE VALUE
----------------- ------- ------
compatible string 18.0.0
noncdb_compatible boolean FALSE
Any ideas? Thanks
I have installed mssql on Ubuntu 16.04. following are the details of sql server.
ms sql (14.0.3015.40-1) i.e SQL server 2017.
when I run the configuration command #sudo /opt/mssql/bin/sqlservr-setup
I got error sudo: /opt/mssql/bin/sqlservr-setup: command not found
I have stopped and restarted but of no use.
When I check the status by command #systemctl status mssql-server
I got
mssql-server.service - Microsoft SQL Server Database Engine
Loaded: loaded (/lib/systemd/system/mssql-server.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Fri 2018-02-02 16:15:29 IST; 4min 20s ago
Docs: https://learn.microsoft.com/en-us/sql/linux
Process: 28050 ExecStart=/opt/mssql/bin/sqlservr (code=exited, status=200/CHDIR)
Main PID: 28050 (code=exited, status=200/CHDIR)
Feb 02 16:15:28 chetan-desktop systemd[1]: mssql-server.service: Unit entered failed state.
Feb 02 16:15:28 chetan-desktop systemd[1]: mssql-server.service: Failed with result 'exit-code'.
Feb 02 16:15:29 chetan-desktop systemd[1]: mssql-server.service: Service hold-off time over, scheduling restart.
Feb 02 16:15:29 chetan-desktop systemd[1]: Stopped Microsoft SQL Server Database Engine.
Feb 02 16:15:29 chetan-desktop systemd[1]: mssql-server.service: Start request repeated too quickly.
Feb 02 16:15:29 chetan-desktop systemd[1]: Failed to start Microsoft SQL Server Database Engine.
I have googled and tried all possible options. But unable to start SQL server.
Please guide me through this.
I had the same two problems.
First, I was referencing very old documentation that applied to an early (preview) release for RHEL, and so I was using the wrong command. The correct command is:
/opt/mssql/bin/mssql-conf setup
Second, the service was failing to start because my virtual machine did not have enough RAM available (SQL Server on Linux requires at least 2GiB of RAM available.) The documentation I was referred to incorrectly stated that only 0.5GiB was required, this is incorrect and journalctl was not providing any useful information about the start failure.
After configuring available memory to 2GiB and using the correct mssql-conf command I was able to successfully configure and start an MSSQL Server instance on Linux.
References:
Configure SQL Server on Linux with the mssql-conf tool (Microsoft Docs)
KB052969: FIX: Minimum memory limit set to 2GB to install or start SQL Server 2017 (Microsoft Support)
Installation guidance for SQL Server on Linux (Microsoft Docs)
The error says that the executable wasn't found in this path, not that the service couldn't start.
According to the installation instructions for Ubuntu you need to run mssql-conf setup to configure the server :
sudo /opt/mssql/bin/mssql-conf setup
not sqlservr-setup
Increasing the RAM size to 3GB on my VM resolved the issue for me.
I am not using eclipse, using GAE SDK to upload my project, problem is when i am trying to upload it is using jre not jdk thats the reason i am getting below error, please help how can i force app engine sdk to use JDK instead of jre
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\j1013366\Desktop\social.login.2013\appengine-java-sdk-1.8.0\appengine-j
ava-sdk-1.8.0\bin>appcfg.cmd update apps/SocialLoginProject
Reading application configuration data...
Jun 05, 2013 12:22:45 PM com.google.apphosting.utils.config.AppEngineWebXmlReade
r readAppEngineWebXml
INFO: Successfully processed apps/SocialLoginProject\WEB-INF/appengine-web.xml
Jun 05, 2013 12:22:45 PM com.google.apphosting.utils.config.AbstractConfigXmlRea
der readConfigXml
INFO: Successfully processed apps/SocialLoginProject\WEB-INF/web.xml
Jun 05, 2013 12:22:45 PM com.google.apphosting.utils.config.IndexesXmlReader rea
dConfigXml
INFO: Successfully processed apps\SocialLoginProject\WEB-INF\appengine-generated
\datastore-indexes-auto.xml
Beginning interaction for server default...
0% Created staging directory at: 'C:\Users\j1013366\AppData\Local\Temp\appcfg152
7926604447976257.tmp'
5% Scanning for jsp files.
8% Compiling jsp files.
Error Details:
Exception in thread "main" java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.apache.jasper.JspCompilationContext.createCompiler(JspCompilation
Context.java:238)
at org.apache.jasper.JspCompilationContext.createCompiler(JspCompilation
Context.java:214)
at org.apache.jasper.JspC.processFile(JspC.java:1181)
at org.apache.jasper.JspC.execute(JspC.java:1341)
at com.google.appengine.tools.development.LocalJspC.main(LocalJspC.java:
40)
Caused by: java.lang.NullPointerException
at com.google.appengine.tools.development.LocalJspC$LocalCompiler.<clini
t>(LocalJspC.java:53)
... 7 more
com.google.appengine.tools.admin.JspCompilationException: Failed to compile jsp
files.
Unable to update app: Failed to compile jsp files.
Please see the logs [C:\Users\j1013366\AppData\Local\Temp\appcfg5225288314554557
20.log] for further information.
C:\Users\j1013366\Desktop\social.login.2013\appengine-java-sdk-1.8.0\appengine-j
ava-sdk-1.8.0\bin>
Personally I have intentionally set it up to use the JRE from within the SDK by modifying appcfg.cmd to
"%JAVA_HOME%\bin\java" -Djava.home="%JAVA_HOME%\jre" -Xmx1100m -cp "%~dp0\..\lib\appengine-tools-api.jar" com.google.appengine.tools.admin.AppCfg %*
and setting JAVA_HOME to point to the JDK.
I am guessing you could modify -Djava.home="%JAVA_HOME%\jre" to point to wherever you like.
The xdebug server doesn't connect to any of the clients on port 9000 ie:Netbeans IDE ,debugclient etc.xdebug is shown in phpinfo output.The above clients keep on waiting for the connection to be established.when ever I try to run a php script from the cli it gives the following warning message:
"PHP Warning: Module 'xdebug' already loaded in Unknown on line 0"
The 9000 port has been opened and shows up in the netstat --numeric-port -l command.
I have no idea what might have gone wrong.I have checked all the configuration files,everything seems ok. Any help will be appreciated.
Section of my configuration files
Linux abc.localdomain 3.1.1-2.fc16.x86_64 #1 SMP Mon Nov 14 15:46:10 UTC 2011 x86_64
This program makes use of the Zend Scripting Language Engine:
Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies
with Xdebug v2.1.2, Copyright (c) 2002-2011, by Derick Rethans
[Zend]
zend_extension=/usr/lib64/php/modules/xdebug.so
[XDebug]
xdebug.remote_enable=On
xdebug.remote_autostart=On
xdebug.remote_handler=dbgp
xdebug.remote_host=localhost
xdebug.remote_port=9000
xdebug.remote_mode=req
xdebug.remote_log=/var/log/xdebug.log
php_api no. coincides
Xdebug Simple DBGp client (0.10.0)
Copyright 2002-2007 by Derick Rethans.
- libedit support: enabled
Waiting for debug server to connect.
Is it black magic!!
Thank You
It was actually Selinux not allowing Httpd to connect to other network resources.
Setting the boolean for httpd solved the problem:
setsebool -P httpd_can_network_connect on
OS Fedora 16-X_64
For me the solution was
sudo chcon -R -h -t /path/to/xdebug.so
meaning SELinux now allows httpd to execute this shared object.