Publishing fails to do anything and leaves no report.

[Rob]

When editing a page, we got an error and found we had no disk space
available on the CMS server. We doubled the disk space and rebooted
the server.

Now we can edit any page, submit to workflow, release and request
publish, but nothing publishes. The publish request shows in the
Current Jobs list when it is waiting but then dispappears after that.
It can't be found in the Job Reports list. No page has published.

Any ideas what could be the cause?

Any ideas to refresh the server, clear out any garbage for a good
restart?

Rob

[Rob]

We are also now getting the following error when we try to Create and
Connect a page:

ExecuteAsync Error in line 0 :Error on
ProcessServer.CreateAndEnqueue:RedDot.CMS.Page.TemplateDefaults.Save;RedDot.CMS.Page.TemplateDefaults.Save;System.Net.Sockets.SocketException:
No connection could be made because the target machine actively
refused it 127.0.0.1:10086 Server stack trace: at
System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32 port)
at
System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(AddressFamily
family) at
System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket() at
System.Runtime.Remoting.Channels.RemoteConnection.GetSocket() at
System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
machinePortAndSid, Boolean openNew) at
System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage
msg, ITransportHeaders requestHeaders, Stream requestStream) at
System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage
msg, ITransportHeaders requestHeaders, Stream requestStream,
ITransportHeaders& responseHeaders, Stream& responseStream) at
System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage
msg) Exception rethrown at [0]: at
System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage
reqMsg, IMessage retMsg) at
System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type) at
RedDot.CMS.ProcessServer.Core.IProcessServer.GetWorker(String
assemblyQualifiedName) at
RedDot.CMS.ProcessServer.Core.Implementation.ProcessServerProxy.GetWorker(String
assemblyQualifiedName) at
RedDot.CMS.ProcessServer.Core.Implementation.Worker.WorkerFactoryBase.Create[T]
() at
RedDot.CMS.Worker.RQL.Proxy.RQLWorkerFactory.CreateAndEnqueue(Int32
priority, String rql, String dllName, String settings, String session,
String queueNamespace, String displayName, String description)

[Jian Huang]

Hi Rob,

The log folder on you CMS application folder is full.  Clear out those logs and you should be fine.  There should also be a user-defined job that comes default with the installation (but deactivate) that cleans this.

[Rob]

Jian,

 

Thanks!  I will follow up on this. 

 

Where do you see indication the log folder is full? 

 

Sorry to not post an update soner.  We found a service on the CMS server did not restart on reboot as it was configured to do.  A manual start resolved the problem we were having. 

 

Rob