Re: pgagent jobs never start - Mailing list pgadmin-support
From | Hogan, James F. Jr. |
---|---|
Subject | Re: pgagent jobs never start |
Date | |
Msg-id | D73D467FE58F004E9D3FA25414945DC10350BFAB@AUSEX3VS1.seton.org Whole thread Raw |
In response to | pgagent jobs never start ("Hogan, James F. Jr." <JHogan@seton.org>) |
List | pgadmin-support |
Thanks to the assistance of Mr. Page my troubles have been solved Adding -l 2 switch the event log showed that there was issue with the pgAgent INSTALL command. I was omitting at the end of the command "password=secrete" After REMOVE and INSTALL with the corrected string All is Well "pgAgent INSTALL -l 2 -u svc_pgsql -p secrete hostaddr=127.0.0.1 dbname=Postgres user=svc_pgsql password=secrete" p.s. don't forget "net start pgAgent" Thanks Dave -----Original Message----- From: Hogan, James F. Jr. Sent: Tuesday, January 17, 2006 9:37 AM To: 'Dave Page' Subject: RE: [pgadmin-support] pgagent jobs never start Wow that was a world of help adding the -l 2 switch... I had some trouble with the "INSTALL" string syntax... Odd thing is I repeated it twice... The missing link was "password=" This is not shown in the documentation I am looking at. Documentation: ************************************** Usage: "C:\Program Files\pgAdmin III\pgAgent" REMOVE <serviceName> "C:\Program Files\pgAdmin III\pgAgent" INSTALL <serviceName>[options] <connect-string> options: -u <user or DOMAIN\user> -p <password> -d <displayname> -t <poll time interval in seconds(default 10)> -r <retry period after connection abort in seconds (>=10, default 30)> -l <logging verbosity (ERROR=0, WARNING=1, DEBUG=2, default 0)> The service may be quite simply installed from the command line as follows: "C:\Program Files\pgAdmin III\pgAgent" INSTALL pgAgent -u postgres -p secret hostaddr=127.0.0.1 dbname=pgadmin user=Postgres *************************************************** HERE IS WHAT I HAD PgAgent INSTALL pgAgent -u svc-pgsql -p secrete hostaddr=127.0.0.1 dbname=Postgres user=svc_pgsql I then added to the end on a wim "password=secrete" And I am up and running Thank you for all your help I hope I am able to help you or someone else out in return some day. I will post a Blurb about this to my original post and also submit a Document update Request to include this "password=" Looks like they indented to as I notice that the string example they provided doesn't have the closing double quote. Again THANK YOU Jim -----Original Message----- From: Dave Page [mailto:dpage@vale-housing.co.uk] Sent: Tuesday, January 17, 2006 4:36 AM To: Hogan, James F. Jr. Cc: pgadmin-support@postgresql.org Subject: RE: [pgadmin-support] pgagent jobs never start > -----Original Message----- > From: Hogan, James F. Jr. [mailto:JHogan@seton.org] > Sent: 16 January 2006 17:41 > To: Dave Page > Subject: RE: [pgadmin-support] pgagent jobs never start > > I did in fact have two separate databases one named > "postgres" the other > named "hogan" > > I was hopeful that you were on to my trouble...However.... > > I have deleted the "hogan" database and created a schema > "hogan" within > the database "posgtres" > > Created a new table within the "hogan" schema > > "hogan".testagent > > Validated that account 'svc_pgsql' has sufficient rights. > > Both server and agent services run under 'svc_pgsql' > > Deleted old job and created new to run every minute > > Insert into "hogan".testagent Values (default, 'hogan') > > Restarted both Windows Services...first the Posgtres Service then the > PGAgent Service > > The New Job still fails to start... > > > > Attached result of > > Pg_dump -f c:\pgagent2.sql -U svc_pgsql postgres > > After changes noted above. OK, loaded that into my master connection DB, installed pgAgent, started it up and away it went inserting rows into the test table. So, I suspect the agent service is failing to connect to your database for some reason. Is there anything obvious in the event log? If not can you remove and add the service again with the -l 2 option please? That will cause a bunch of debug output to be logged to the Application event log, and should include some hints as to what's going on. Regards, Dave.
pgadmin-support by date: