Apache2 restart failed after trunk update

[Psycholiquid]

@Wayne-Workman Also where is the cert located in the OS?

[Psycholiquid]

I’m assuming this is the cert? /fog/management/other/ssl/srvpublic.crt

[Wayne Workman]

@Psycholiquid you need the CA. The certs are actually regenerated on every install, to my understanding.

[Psycholiquid]

So I’m lost I need it to regenerate or I need to replace with the backed up one

[Tom Elliott]

@Psycholiquid validity period, can you make sure the windows and fog servers are matching with their time? As you do tend to rely on snapshots of course.

[Tom Elliott]

@Wayne-Workman ca and private key is not regenerated every install, just the csr and public cert.

[Wayne Workman]

@Tom-Elliott That’s what I meant.

[Psycholiquid]

OK so what would I need to do to resolve this. I am in another state trying to get the node working so I dont have to touch every machine but cant due to this.

[Psycholiquid]

I mean I could roll back but I would rather move forward. The times seem to be just fine so far as I can tell. but my server is being slammed now due to bad requests.

[Psycholiquid]

Just verified the dates and times are matching perfectly

[Psycholiquid]

Update:

So it leads me to believe that it is something on the client now? I am really lost on this.

Getting this now:

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/1/2016 8:18 AM Client-Info Version: 0.9.11
 3/1/2016 8:18 AM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 3/1/2016 8:18 AM Data::RSA FOG Server CA cert found
 3/1/2016 8:18 AM Middleware::Authentication Cert OK
 3/1/2016 8:18 AM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 3/1/2016 8:18 AM Middleware::Communication Response: Invalid security token
 3/1/2016 8:18 AM Service Sleeping for 120 seconds```

[Psycholiquid]

Update:

So I went through the though that with the last error maybe it needed to be reinstalled on the client. Did that and then reset the encryption data on the host from the interface. That seems to clear the error, now I am getting different errors on that host. Please see below. Seems to run in circles.

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/1/2016 8:28 AM Client-Info Version: 0.9.11
 3/1/2016 8:28 AM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 3/1/2016 8:28 AM Data::RSA FOG Server CA cert found
 3/1/2016 8:28 AM Middleware::Authentication Cert OK
 3/1/2016 8:28 AM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 3/1/2016 8:29 AM Middleware::Communication Response: Invalid security token
 3/1/2016 8:29 AM Service Sleeping for 120 seconds

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/1/2016 8:31 AM Client-Info Version: 0.9.11
 3/1/2016 8:31 AM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 3/1/2016 8:31 AM Data::RSA FOG Server CA cert found
 3/1/2016 8:31 AM Middleware::Authentication Cert OK
 3/1/2016 8:31 AM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 3/1/2016 8:31 AM Middleware::Communication Response: Success
 3/1/2016 8:31 AM Middleware::Authentication Authenticated

 3/1/2016 8:31 AM Bus Registering ParseBus in channel Power

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 3/1/2016 8:31 AM Client-Info Version: 0.9.11
 3/1/2016 8:31 AM ClientUpdater Running...
 3/1/2016 8:31 AM Middleware::Communication URL: http://fog-server/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=00:50:56:86:1F:C7||00:00:00:00:00:00:00:E0&newService=1
 3/1/2016 8:31 AM Middleware::Communication Response: Success
 3/1/2016 8:31 AM Middleware::Communication URL: http://fog-server/fog/service/getversion.php?client&newService=1
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 3/1/2016 8:31 AM Client-Info Version: 0.9.11
 3/1/2016 8:31 AM TaskReboot Running...
 3/1/2016 8:31 AM Middleware::Communication URL: http://fog-server/fog/service/servicemodule-active.php?moduleid=taskreboot&mac=00:50:56:86:1F:C7||00:00:00:00:00:00:00:E0&newService=1
 3/1/2016 8:31 AM Middleware::Communication Response: Success
 3/1/2016 8:31 AM Middleware::Communication URL: http://fog-server/fog/service/jobs.php?mac=00:50:56:86:1F:C7||00:00:00:00:00:00:00:E0&newService=1
 3/1/2016 8:31 AM Middleware::Communication Response: Invalid host certificate
 3/1/2016 8:31 AM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 3/1/2016 8:31 AM Data::RSA FOG Server CA cert found
 3/1/2016 8:31 AM Middleware::Authentication Cert OK
 3/1/2016 8:31 AM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 3/1/2016 8:31 AM Middleware::Communication Response: Success
 3/1/2016 8:31 AM Middleware::Authentication Authenticated
 3/1/2016 8:31 AM Middleware::Communication URL: http://fog-server/fog/service/jobs.php?mac=00:50:56:86:1F:C7||00:00:00:00:00:00:00:E0&newService=1&newService=1
 3/1/2016 8:31 AM Middleware::Communication Response: Invalid host certificate
 3/1/2016 8:31 AM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 3/1/2016 8:31 AM Data::RSA FOG Server CA cert found
 3/1/2016 8:31 AM Middleware::Authentication Cert OK
 3/1/2016 8:31 AM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 3/1/2016 8:31 AM Middleware::Communication Response: Success
 3/1/2016 8:31 AM Middleware::Authentication Authenticated
 3/1/2016 8:31 AM Middleware::Communication URL: http://fog-server/fog/service/jobs.php?mac=00:50:56:86:1F:C7||00:00:00:00:00:00:00:E0&newService=1&newService=1&newService=1
 3/1/2016 8:32 AM Middleware::Communication Response: Invalid host certificate
 3/1/2016 8:32 AM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 3/1/2016 8:32 AM Data::RSA FOG Server CA cert found
 3/1/2016 8:32 AM Middleware::Authentication Cert OK
 3/1/2016 8:32 AM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 3/1/2016 8:32 AM Middleware::Communication Response: Success
 3/1/2016 8:32 AM Middleware::Authentication Authenticated
 3/1/2016 8:32 AM Middleware::Communication URL: http://fog-server/fog/service/jobs.php?mac=00:50:56:86:1F:C7||00:00:00:00:00:00:00:E0&newService=1&newService=1&newService=1&newService=1
 3/1/2016 8:32 AM Middleware::Communication Response: Invalid host certificate
 3/1/2016 8:32 AM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 3/1/2016 8:32 AM Data::RSA FOG Server CA cert found
 3/1/2016 8:32 AM Middleware::Authentication Cert OK
 3/1/2016 8:32 AM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 3/1/2016 8:32 AM Middleware::Communication Response: Success
 3/1/2016 8:32 AM Middleware::Authentication Authenticated
 3/1/2016 8:32 AM Middleware::Communication URL: http://fog-server/fog/service/jobs.php?mac=00:50:56:86:1F:C7||00:00:00:00:00:00:00:E0&newService=1&newService=1&newService=1&newService=1&newService=1
 3/1/2016 8:32 AM Middleware::Communication Response: Invalid host certificate
 3/1/2016 8:32 AM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
 3/1/2016 8:32 AM Data::RSA FOG Server CA cert found
 3/1/2016 8:32 AM Middleware::Authentication Cert OK
 3/1/2016 8:32 AM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
 3/1/2016 8:32 AM Middleware::Communication Response: Success
 3/1/2016 8:32 AM Middleware::Authentication Authenticated
 3/1/2016 8:32 AM Middleware::Communication URL: http://fog-server/fog/service/jobs.php?mac=00:50:56:86:1F:C7||00:00:00:00:00:00:00:E0&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1

[Wayne Workman]

Bringing in the big guns to maybe shed light on what’s going.
Informing @Jbob

[Psycholiquid]

@Wayne-Workman Yeah it is very weird, its like it wants to work, but then it gets all confused. I did manually install the client. But I see where it is trying to run also.

[Wayne Workman]

@Psycholiquid Is fog-server your fog server’s actual name and is there a DNS entry for it?

[Psycholiquid]

@Wayne-Workman it is a cname but it works no problem, I can ping it from anywhere on the network. It is not however the server name. I was using IP addresses before but didnt like that. But this has been in place for about 8 months now

[Wayne Workman]

@Psycholiquid If it were me in your position - I would roll back to when it was working,

And I would copy /opt/fog/snapins/CA to /root for safe keeping, I’d also copy /opt/fog/snapins/ssl to /root.

cp -r /opt/fog/snapins/CA /root
cp -r /opt/fog/snapins/ssl /root

I know that it wasn’t long ago that all the paths and stuff changed for the CA and ssl directories - so you’ll just need to pay close attention to those after you update forwards.

This should take no time. Roll back, backup your CA and ssl folders, update to the latest. Check everything.

However it’s perfectly fine if you want to wait for further input from Tom or Jbob and I’d take zero offense from that.

[Psycholiquid]

Yeah I will wait but I agree making a backup of those is not a bad idea at all.

[Psycholiquid]

Any ideas guys? OR should I just roll back?

[Psycholiquid]

For now I have rolled back to the working version. Let me know if anyone has any ideas.

@Wayne-Workman I have now made a backup for those files we were discussing.