That’s a pretty cool setting.. Don't even need to tweak the registry if you
do not want to, to create service dependencies..
1) Is that really not documented anywhere? When was it introduced? What does
the V in the V_WAIT_BEFORE_STARTUP stand for?
2) While it’s a nice setting that would get you there perhaps 90% of the
time, it would be even nicer if the design around this was something like,
this variable to accept a string instead of a numeral, and this string be a
stored procedure that returned an expected known value. This way would be a
100% method of knowing the SQL server is up and more importantly
"responding"...
Just my two cents..
Joe
-----Original Message-----
From: Longwing, LJ CTR MDA/IC
Sent: Wednesday, June 13, 2012 9:28 AM Newsgroups:
public.remedy.arsystem.general
To: [email protected]
Subject: Re: Remedy Startup
Ok Mark, first off, Thank you, that worked the miracle that I needed.
Secondly, why isn't that documented anywhere? I have spent roughly 10-15
hours trying to 'fix' this particular problem reading every document I can
find, scouring the web, utilizing countless resources to try and do exactly
what you just gave me, all to no avail because this option isn't documented.
If it had been it may have been an hour or two...but I certainly would have
found this documented SOMEWHERE and applied the fix.
Thirdly, what other 'gems' does BMC have hidden way in un-documented
features that the average or advanced user of the system would find
EXCEEDINGLY useful if they only knew it was an option
Thank you again...you just pulled yet another thing off of my plate, and for
that I'm truly appreciative...I can now move onto bigger and more important
things :)
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Walters, Mark
Sent: Wednesday, June 13, 2012 7:12 AM
To: [email protected]
Subject: Re: Remedy Startup
There's an environment variable that you can set to a numerical value -
V_WAIT_BEFORE_STARTUP - that will be read by armonitor and it will wait that
many seconds before it starts the server. For example,
V_WAIT_BEFORE_STARTUP=300 would be a 5 minute delay. One thing to note
though is that this delay will happen on every restart of the Remedy
service, which can be a nuisance if you want to just bounce the service once
it has been running for a while.
The variable needs to be set at the system level so that the service can
read it and I think a reboot is required when it is set/changed.
Mark
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Longwing, LJ CTR MDA/IC
Sent: 13 June 2012 13:58
To: [email protected]
Subject: Re: Remedy Startup
Andrew,
You are correct....SQL Server is reporting itself as online, when it's not
fully available, and this is screwing up Remedy because it's trying to
connect to a DB that's not yet available. I'm looking for a way to delay
that startup
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Andrew Fremont
Sent: Tuesday, June 12, 2012 3:13 PM
To: [email protected]
Subject: Re: Remedy Startup
** It could be that the SQL service is not up yet by the time AR start.
It happened on one of our dev machines after rebooting where both AR and SQL
are installed.
Andrew.
On Tue, Jun 12, 2012 at 2:03 PM, Longwing, LJ CTR MDA/IC
<[email protected]> wrote:
Ok...my box is running Remedy and SQL Server both and on startup the Remedy
service fails to start properly. The arerror.log shows an error about
ARAdmin login failing twice, then the process dies. An immediate attempt to
start the service functions fine. Checking the SQL Logs I see something
along the lines of
12:00:00 Starting ARSystem
12:00:01 Attempted login from ARAdmin failed
12:00:02 Scanning ARSystem
12:00:06 Recovery of ARSystem complete
That's not a copy of the log (because I can't get that to the
internet)...but that's close to what it says....this is only happening on
one of my boxes, and I suspect that it's a memory related issue because when
I check a functional box, I see everything except the login failed line, but
it all happens within a second of each other...and my remedy doesn't have
any problems starting. I have the Remedy service set to depend on the SQL
service, but according to the internet (and my personal experience) the SQL
Service reporting as 'up' does not mean that DB's are available. MS
recommends that if you need to 'delay' the startup of a particular service
that you should set it dependent on 'Spooler'...I've done this but it
doesn't help...I need another 5-10 seconds delay with the attempted starting
of Remedy service....any recommendations?
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
