next time to check 1969

[rushowr]

I've searched the forums and found other references to this but none of them apply. I posted before, and that helped but this time I have a slightly different issue.

I'm doing a UserParameter asterisk[checkswitch1] using a valid command that zabbix can use. When I add it to the frontend, I get a 1969 time (1 sec before unix time zero) and it holds everything else in the queue up as well.

This is a mission critical monitoring command, using sipsak (usable by all users and in the standard /usr/bin location. nothign is privileged about the command. also, I doublechecked the UserParameter, and it matches.

I'm using zabbix 1.0 on CentOS 4.

Any ideas? This only happens on an occasional new item, and usually creating an item with a different name works, but not this time.

[rushowr]

no one has ever had this problem? Nothing even similar?

[nihilist]

I just did. Fresh install, took me about 30 minutes to figure out how to make things work. I assume that I have it setup properly, though I really don't know. I've got the server and agent running on the same machine for testing.

[rushowr]

Here's a fix...simple too, can't believe I didn't notice it...sorry I forgot to reply to my post...


Make sure zabibx_suckerd is running on the server.
On a whim I decided to log into the server to see if the agentd was running, and found that suckerd wasn't. The 1969 dissapeared after I started suckerd and disabled and enabled the item(s) with the 1969 time frame.

[nihilist]

Ah, I'm using 1.1. In my case, I didn't populate the "key" field with a proper value (serves me right for not reading the manual completely), and that borked things.

[mdasilva]

Same problem, fresh install

just installed 1beta7 and nothing is being sent out.. all checks are stuck in queue with the next send in year 1969? whats the solution?