HTTP status 503: Service Unavailable
Moderator: SourceGear
HTTP status 503: Service Unavailable
Hi,
We seem to be getting the below log entry a lot (every couple of minutes).
----16/04/2007 13:37:37 xxx--xxx.xxx.com(xxx.xxx.xxx.xxx)--SSL Disabled Exception in plugin thread : The request failed with HTTP status 503: Service Unavailable.
Vault seems to be running more or less fine, though.
Any ideas how I can stop this?
Regards,
Tilman
We seem to be getting the below log entry a lot (every couple of minutes).
----16/04/2007 13:37:37 xxx--xxx.xxx.com(xxx.xxx.xxx.xxx)--SSL Disabled Exception in plugin thread : The request failed with HTTP status 503: Service Unavailable.
Vault seems to be running more or less fine, though.
Any ideas how I can stop this?
Regards,
Tilman
Hi again,
We now moved the Vault server onto a different machine. The thing is, now the tblplugins table only contains the URL of the old machine and the shadow folder log says
5/9/2007 10:47:40 AM <generic>: [<No Name>:3724] GetEntryAssembly() returned null; not logging assembly name
5/9/2007 10:47:43 AM <generic>: [<No Name>:3268] SimpleLogger finalized
over and over.
Any ideas how to solve this?
Tilman
We now moved the Vault server onto a different machine. The thing is, now the tblplugins table only contains the URL of the old machine and the shadow folder log says
5/9/2007 10:47:40 AM <generic>: [<No Name>:3724] GetEntryAssembly() returned null; not logging assembly name
5/9/2007 10:47:43 AM <generic>: [<No Name>:3268] SimpleLogger finalized
over and over.
Any ideas how to solve this?
Tilman
Did you create new shadow folder associations with the Admin Tool after you moved the Vault Server?
It's possible there's not more info in the log because shadow folders aren't set up.
Did you have debug logging enabled in the old Vault Server installation? The new installation created a new shadow folder web.config file, where shadow folder associations and other config info is kept.
You can enable debug logging for the shadow folder service by uncommenting this line in the Vault Shadow Folder Service web.config file:
<add key="classesToLog" value="" />
For initial troubleshooting, you can log "all" classes:
<add key="classesToLog" value="all" />
It's possible there's not more info in the log because shadow folders aren't set up.
Did you have debug logging enabled in the old Vault Server installation? The new installation created a new shadow folder web.config file, where shadow folder associations and other config info is kept.
You can enable debug logging for the shadow folder service by uncommenting this line in the Vault Shadow Folder Service web.config file:
<add key="classesToLog" value="" />
For initial troubleshooting, you can log "all" classes:
<add key="classesToLog" value="all" />
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
We copied the associations from the old web.config. They then showed up in the admin tool.Did you create new shadow folder associations with the Admin Tool after you moved the Vault Server?
I enabled debug logging, but it doesn't seem to make a difference.
Should there be an entry for the new machine in the tblplugins table?
Thanks,
Tilman