Velocis daemon error - the daemon is probably not running (4437 Views)
Reply
Frequent Advisor
Miguel Carranza
Posts: 33
Registered: ‎03-31-2004
Message 1 of 7 (4,437 Views)

Velocis daemon error - the daemon is probably not running

Velocis crashes after a short period of time after backup session start.
These are some of the errors reported:

Query incomplete/failed ([12:1166] Velocis daemon error - the daemon is probably not running.)

[Critical] From: BSM@consola.sigmaq.com "PRO47_DBARCH" Time: 2/16/2009 6:45:14 AM
[61:4001] Error accessing the database, in line 1254, file x:\src\sm\bsm2\bcsmutil.c.
Database subsystem reports:
"[12:1165] Internal Database network communication error."

Additionaly I am not able to perform extended checks on the db, since the service since the "Data Protector RDS" Service crashes at the start of the check (omnidbcheck -extended).
Any ideas?
Esteemed Contributor
Prashanth Waugh
Posts: 620
Registered: ‎05-17-2007
Message 2 of 7 (4,437 Views)

Re: Velocis daemon error - the daemon is probably not running

Hi,
Pls check the status of DP demons
#omnisv -status
if the any demon is not running then you can use
#omnisv -stop
#omnisv -start
#omnisv -status
but be careful while excuting the omnisv -status command that time any backup session should not run

Regards
Prashant
For success, attitude is equally as important as ability
Esteemed Contributor
Prashanth Waugh
Posts: 620
Registered: ‎05-17-2007
Message 3 of 7 (4,437 Views)

Re: Velocis daemon error - the daemon is probably not running

Hi,

one mistake in above post

be careful while running
omnisv -stop

Reagrds
Prashant
For success, attitude is equally as important as ability
Frequent Advisor
Miguel Carranza
Posts: 33
Registered: ‎03-31-2004
Message 4 of 7 (4,437 Views)

Re: Velocis daemon error - the daemon is probably not running

Thanks for your reply.
I finally determined that the "filenames" and "core" db were corrupted. After a few hours, I found this procedure to export/import the db.

http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1234887403376+28353475&...

Apparently, as part of the process the db corruption is fixed as well.
HP Tech support also sent me the attached document with a similar procedure.
Frequent Advisor
Miguel Carranza
Posts: 33
Registered: ‎03-31-2004
Message 5 of 7 (4,437 Views)

Re: Velocis daemon error - the daemon is probably not running

This procedure fixed my db.
Backups are running normaly.
Velocis is not crashing anymore.
I am now able to run db tests/checks without problems.
Frequent Advisor
Nancy A Sherman
Posts: 46
Registered: ‎07-15-2008
Message 6 of 7 (4,437 Views)

Re: Velocis daemon error - the daemon is probably not running

Hi Miquel
Now that you have been running for a few months after you fixed your db corruption, have you seen the error again?

I have been getting this error since December, and its very intermittent
HP told us in March:

This issue is caused by a combination of stale sessions and a particular limit set in the /var/opt/omni/server/db40/datafiles/catalog/rdmserver.ini file.

We changed the setting per HP - and error is still occuring.....

I'm wondering now if we have coruption - like you did -

How long did it take you to export and re-import your database?

Thanks for the advice.
Nancy Sherman
Sabic Plastics
Frequent Advisor
Miguel Carranza
Posts: 33
Registered: ‎03-31-2004
Message 7 of 7 (4,437 Views)

Re: Velocis daemon error - the daemon is probably not running

My db is only 4gb, so the process took about an hour (if I recall correctly).
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.