Recently, there is a host which indicates me the error message :
Get value from agent failed: cannot connect to [] interrupted system call
I do not understand what happens to it, this host uses an agent zabbix on the port 10050.
Except that on my 10 other hosts which are also with a zabbix agent there is no problem, it's really only on one that I have this problem.
I've tried to search on the web but nothing works.
Could it be a problem with the agent installed on the host?
Related
I am trying to intergrate our mattermost with zabbix to receive notifications on alerts. I've followed up the instructions on this link. We are using Zabbix 4.4 with MM 5.19.
After enabling the integration, No alerts are being posted on Mattermost. I tried testing the Media type on Administration > Media Types > Mattermost > Test.
I've added the following as the parameters, but it throws the error : Connection timeout of 3 seconds exceeded when connecting to Zabbix server "localhost".
bot_token : {Token generated for the Bot in Mattemost}
mattermost_url : {https://mattermost.our-company.com}
send_mode : alarm
Tried changing {ZABBIX_URL} to both http://127.0.0.1 and http://zabbix.our-company.com (The DNS is resolved only internally, but our mattermost is available on public network) but none of them work.
I checked the logs inside /var/log/zabbix but no error or anything. I even tried putting the zabbix logs to Debug mode but no luck in any case, the only Debug log I've got is the following :
2063:20200216:090224.146 trapper got '{"request":"alert.send","sid":"74095b240dd6783618571516f029187a","data":{"parameters":{"zabbix_url":"{$ZABBIX.URL}","send_mode":"alarm","send_to":"{ALERT.SENDTO}","event_tags":"{EVENT.TAGS}","event_name":"{EVENT.NAME}","event_nseverity":"{EVENT.NSEVERITY}","event_ack_status":"{EVENT.ACK.STATUS}","event_value":"{EVENT.VALUE}","event_update_status":"{EVENT.UPDATE.STATUS}","event_date":"{EVENT.DATE}","event_time":"{EVENT.TIME}","event_severity":"{EVENT.SEVERITY}","event_opdata":"{EVENT.OPDATA}","event_id":"{EVENT.ID}","event_update_message":"{EVENT.UPDATE.MESSAGE}","trigger_id":"{TRIGGER.ID}","trigger_description":"{TRIGGER.DESCRIPTION}","host_name":"{HOST.NAME}","host_ip":"{HOST.IP}","event_update_date":"{EVENT.UPDATE.DATE}","event_update_time":"{EVENT.UPDATE.TIME}","event_recovery_date":"{EVENT.RECOVERY.DATE}","event_recovery_time":"{EVENT.RECOVERY.TIME}","bot_token":"qs3rkqdappy6i8gs3a8871phxc","mattermost_url":"https:\/\/mattermost.our-company.com"},"mediatypeid":"7"}}'
What can be the issue? Is there a way to "debug" and find the root cause of this error? Any help is appreciated! Note that right now we have integrated Slack with Zabbix and it's working fine, but we are moving to Mattermost and therefore, we need to migrate the integrations as well.
We found out the issue with our Network Admin. The problem was that our Zabbix server was trying to resolve Mattermost name from local network route (i.e. 192.168.x.x) and it kept failing, therefore, no SSL connection could be initiated.
It seems that Zabbix integration tests' error messages are quite generic and sometimes, misleading. Thorough investigation is needed for finding out the root cause.
Apologies if this is a bit basic:
I have a Google Compute Instance running Windows Server 2012 R2. It has a valid admin account and password (checked via gcloud). The external IP address can be pinged, the system has been stopped and started successfully. The gcloud commands execute successfully etc etc.
If I try to RDT in I get the unsuccessful message. If I use the RDT (Chrome) option in the Google Cloud Platform admin page I get this message:
In order to use the Chrome RDP Extension, you must configure VM
instance so that it has an external IP address, username and password.
Note: You must configure the network firewall to open TCP port 3389 to
enable RDP access.
Note that ALL of the above are correct and confirmed.
I am sort of going round in circles, I've tried to use powershell on a windows system to RDT in to no avail. Again, using the built in Bash serial access I can get to the system and, for example, retrieve the admin account and password, BUT RDT FAILS.
I have tried using the powershell command Enter-PSSEssion... and I initially got a winrm error, apparently the IP address needs to be in trustedhosts. Fixed that and now I am getting a message that I need to verify that winrm is running on the destination computer, catch 22, that's why I'm using winrm, to access the destination computer.
Any ideas what I might try next?
Thanks.....
create a rdp network tag for firewall rule, which allows tcp:3389 ingress and and then apply it to the instance in question... someone (assuming you're at work) might have removed/edited these rules trough the console or gcloud command.
I used zabbix 2.4 and it worked perfectly. I decided to upgrade server and all agents to 3.0 LTS. I did not change any settings in agents and server conf-files and did not change any settings wia web.
But now I receive messages
Zabbix agent %servername% on is unreachable for 5 minutes
This agent works on the same machine with zabbix-server. More strange that I receive other messages from this agent. So I can see that agent works and server can communicate with it.
After I started to receive this error message I tried to change IP of agent. First it was 127.0.0.1, after I changed address to network's IP: 192.168.x.x. Nothing changed. I receive unreachable message every 6-7 minutes with the other messages from this agent. And also this agent is green via web-interface.
zabbix_get -s 127.0.0.1 -k agent.ping
also returns 1.
How to fix problem?
I increased Timeout and error has gone
take zabbix server restart and it will work.
You can check also zabbix_agentd.conf and replace valid IP and name
i'm having a problem sending the mesurements to the contextBroker.
I have the ContextBroker running on a CentOS virtual machine. On another CentOS virtual machine i'm setting the figway config.ini file with the host=/ContextBroker Virtual Machine Host IP/ and Port=1026. When i send mesurements to my ContextBroker:
python2.7 SendObservation.py Bus1 't|1'
it simply doesn't stick the values to the entity. It gives me a code:200 but the response is just blank.
What am i doing wrong?
UPDATE:
Even when i do from one VM to another (to the one where the contextBroker is running) the command:
GET *ip*:1026/version
, it returns nothing.
UPDATE:
Running
GET localhost:1026/version
works. Returns what's supose to return.
The problem could be similar to the one described in the answer to this question. The most probable causes of Orion connection problems are:
Something in the Orion host (e.g a firewall or security group) is blocking the incoming connection
Something in the client host (e.g a firewall) is blocking the outcoming connection
There is some other network issue is causing the connection problem.
I've created an SSIS package which runs perfect when scheduled as a job.Now I've have a requirement that a mail ought to be sent every time it runs stating if the package was successfully completed or failed.
I've created an SMTP Connection with server name as mx.xxxxxxxx(organization).I've neither checked windows authentication or Enable Secure Socket Layer Options(as suggested in various blogs).
The Job runs fine and sends mail when run manually but is failing when scheduled as a job.
I've tried running it by editing the command line as suggested by many but with no success.
Can you please suggest where I might be going wrong,
Below is the error:
Argument "SMTP" for option "connection" is not valid. The command line parameters are invalid. The step failed.
Since it fails when you run it from your production server, regardless of whether you run it manually or from the job, it is probably related either to connectivity (can your production server connect to the smtp server), or it could be permissions related, if you are using some kind of proxy account on the server that is different from the one you use in your local BIDS.