VXVM_TRANS_MAX_TIMEOUT variable

[rccmum]

Does anyone know where this environment variable is set? how and where to define it with a value?

I getting this error occasion

vxvm:vxconfigd: [ID 644802 daemon.warning]
V-5-1-11550 Timed out transaction for client 14079. Try setting the environment variable VXVM_TRANS_MAX_TIMEOUT (600) to a higher value and restart vxconfigd.

[James R. Ferguson]

Hi:

I would do:

# grep VXVM_TRANS_MAX_TIMEOUT /etc/rc.config.d/*

...under the assumption that the daemon is started as an rc script during startup.

Regards!

...JRF...

[Sameer_Nirmal]

Thanks. It's not there.

[Sameer_Nirmal]

Oops... Apologize for wrong entry.

[rccmum]

Hi James,

I looked in the rc.config.d directory but couldn't find the variable.

Any idea?

[rccmum]

Anyone?

[rccmum]

Any help I can use?

Thanks

[Patrick Wallek]

Have you tried Veritas' web site? The fact that it is VXVM leads me to believe that it may be related to the Veritas Volume manager.

[VK2COT · Accepted solution]

Hello,

Sadly, you will not find many references
to VxVM environment variables.

This question was asked several times in
Symantec/Veritas and Sun/Solaris forums -
nobody answered.

Put it simply, VXVM_TRANS_MAX_TIMEOUT is yet
another environment variable, which you
are supposed to set up within your
profile, or Shell scripts.

I would set it up in the RC script before
vxconfigd is started.

Cheers,

VK2COT

[chris huys_4]

Hi,

I wouldnt change anything, until I knew, what causes the message to be logged, what the impact of the message is, and, if there is a serious impact, how to solve it.

And for that, you will need to log a call with support.

Best Regards,
Chris

[rccmum]

Contacted Symantec. Per them this env variable can be set just like any other env variable but all VxVM commands would take more time to complete.

It turned out to be BCV agent causing this problem.

[rccmum]

Thanks.