I've got some bizzare & annoying problem in some of our servers.All other servers dont have this unknown restart issue. Only the PPPoEservers restart. When it restarts, it shows this message:
"kernel: Dazed and confused, but trying to continue Do you have a strange power saving mode enabled?"
I did searches on google, didn't find anything regarding this issue,but i found few similar searches; there were unknown solutions forthis. Some showed that it was something to do with the RAM, but ichecked that, it doesn't have anything to do with it.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
It is getting restarted on it's own? If so, it sounds like you have a driver conflict and you've setup your system to simply restart when there is a crash. Enable the crash dump to capture the Blue Screen information the next time the server restarts. Please provide the version of vSpace you're using.
I had exactly the same issue, its basically your iDrac card thats likely at fault. I simply removed mine and the server would boot as expected. If you require the iDrac then order a new card and this should solve your issue.
It seems that your hard drive is restarting because of an unknown reason. I would recommend to check your hard drive's power connector, maybe there are connection problems. If you have free connectors then use another one and see if problem occurs again. Good luck!
If this is the solution for your problem, please rate my post, otherwise give us more details.
The issue usually manifests itself with a line in the SystemOut.log or equivalent reporting the following: WSVR0605W: Thread "THREAD NAME : ID" (55c8824f) has been active for 600,112 milliseconds and may be hung. There are 1 threads in total in the server that may be hung.
If you do a thread dump in your App Server at this point, you will see something like so:
- waiting on <0x93d29020> (a java.lang.Object) at java.lang.Object.wait(Object.java:429) at com.crystaldecisions.thirdparty.com.ooc.OB.Downcall.waitUntilCompleted(Downcall.java:831) - locked <0x93d29020> (a java.lang.Object) at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPClientWorkerThreaded.receive(GIOPClientWorkerThreaded.java:327) at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPClientWorkerThreaded.sendReceive(GIOPClientWorkerThreaded.java:353) at com.crystaldecisions.thirdparty.com.ooc.OB.Downcall.request(Downcall.java:336) at com.crystaldecisions.thirdparty.com.ooc.OB.DowncallStub.invoke(DowncallStub.java:583) at com.crystaldecisions.thirdparty.com.ooc.CORBA.Delegate.invoke(Delegate.java:579) at com.crystaldecisions.thirdparty.org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:125) at com.crystaldecisions.enterprise.ocaframework.idl.OCA.OCAi._InfoStoreEx3Stub.queryEx3(_InfoStoreEx3Stub.java:62) at com.crystaldecisions.enterprise.ocaframework.j.a(Unknown Source) at com.crystaldecisions.enterprise.ocaframework.j.find(Unknown Source) at com.crystaldecisions.enterprise.ocaframework.AbstractServerHandler.buildServerInfo(Unknown Source) at com.crystaldecisions.enterprise.ocaframework.AbstractServerHandler.buildClusterInfo(Unknown Source) at com.crystaldecisions.enterprise.ocaframework.aa.for(Unknown Source) at com.crystaldecisions.enterprise.ocaframework.ServiceMgr.for(Unknown Source) at com.crystaldecisions.enterprise.ocaframework.o.a(Unknown Source) at com.crystaldecisions.enterprise.ocaframework.o.a(Unknown Source) at com.crystaldecisions.enterprise.ocaframework.o.a(Unknown Source) at com.crystaldecisions.enterprise.ocaframework.p.a(Unknown Source) at com.crystaldecisions.enterprise.ocaframework.ServiceMgr.getManagedService(Unknown Source) at com.crystaldecisions.sdk.occa.managedreports.ras.internal.CECORBACommunicationAdapter.connect(Unknown Source) at com.crystaldecisions.sdk.occa.managedreports.ras.internal.RASReportAppFactory.a(Unknown Source) at com.crystaldecisions.sdk.occa.managedreports.ras.internal.RASReportAppFactory.a(Unknown Source) at com.crystaldecisions.sdk.occa.managedreports.ras.internal.RASReportAppFactory.openDocument(Unknown Source) at com.crystaldecisions.sdk.occa.managedreports.ras.internal.RASReportAppFactory.openDocument(Unknown Source) at com.talic.pi.utils.ReportingEngine.generateReport(ReportingEngine.java:86) at com.talic.pi.cms.dao.ReportsDAO.generateReport(ReportsDAO.java:31) at com.talic.pi.cms.component.ReportGeneratorComponentImpl.generateReport(ReportGeneratorComponentImpl.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.ibm.ws.sca.internal.java.handler.JavaReflectionAdapter$2.run(JavaReflectionAdapter.java:152)
The cause: This is mainly caused by reports that take a great deal of time to execute causing the application server to report that the processing thread is 'hung'. A worse side effect of this is when the application server runs out of threads and is unable to process any further requests due to these hung threads.
The solution: The problem is due to the fact that the Corba Timeout has not been set. You've missed the clientSDKOptions.xml in your deployment. This causes the RAS SDK to probably never timeout its call to the RAS.
Create a file called clientSDKOptions.xml and place it in your application's WEB-INF/classes folder, or alternatively, you could place it in a server wide classpath folder like 'applib' on OC4J or $WASPROFILE/properties on WebSphere. The contents of the file should be as follows:
Ok, so working thru the troubleshooting model you have identified the symptoms fairly well but I dont know if you have adequately identified the area affected. In order for the copiers to create a file on a network server they need user names and passwords to access a network resource and they need sufficient rights to create a file. Have you tried to log into the scan folder on the server using the copiers credentials from a workstation?
The next step, of course is to identify what has changed.If you had a problem with a domain controller is it possible the user accounts for the copiers got deleted/damaged/modified?
Log into the internal web page of the copier by plugging its ip address into the address bar of your favourite web browser and verify that its network settings (dns server, domain name, etc) are correct. I believe you can ping the server from the web page as well, if not it can be done from the tcp/ip setup screen on the copier control panel.
There is no way to manually flush the DNS cache on the copiers except for powercycling the device, just make sure you are turning it off by the main power switch near the back of the machine and not the on-off button on the control panel.
I dunno if this qualifies as a solution or a clarification request but I would start with the user accounts and access permissions.