Posts made by apathetic_admin

@Wayne-Workman That seemed to make it happy, thanks.

@Tom-Elliott I’m lost too. So this file doesn’t exist, is this something new that’s being added? I just want to avoid breaking anything.

@Tom-Elliott If it is supposed to be there shouldn’t I already be seeing issues with it while it’s been running on 6267?

Re: 6267 installfog.sh fails at Creating SSL Certificate

I tried this a few months ago and had the same issue, and I’ve not had a chance to get back to it until today.

Relevant output from console:

* Creating SSL Certificate....................................Failed!

Relevant output from error log:

/opt/fog/snapins/ssl//fog.csr: No such file or directory

The file fog.csr did not exist in that location (or on the entire filesystem that I can find) before I started the upgrade process.

A similar issue was resolved by someone else on the forums by using the recreate flag, but I don’t imagine that I’d want to recreate it if I can avoid it.

@Wayne-Workman …It was really just that easy. I am so good at computers…

Thanks

We are hoping to trial Windows 10 to our users soon. We have Dell Latitude E6540s that we are pushing our Windows 10 Enterprise image to. Secure boot is disabled, and it’s set to legacy boot (as opposed to UEFI). Once FOG deploys the image, the laptop reboots. Then it network boots, loads the FOG menu, and then exits to boot to the hard drive. At this point the screen stays black, and then laptop beeps once. If I disable network boot, or I disconnect the ethernet cable, the laptop boots as expected and Windows 10 completes installation as I would expect. I tried the kernel named “Kernel - 4.4.2 TomElliott” from 2/23/16 in hopes that a newer kernel would resolve the issue but it did not. These laptops do successfully work with Windows 7, so I’m theorizing that this is an issue between the Windows 10 boot loader and the way that the FOG menu/kernel is handing off to it. I’ve seen a couple other posts here and there regarding similar issues but have found no resolution.

Anybody have any suggestions?

Was just updating, not a new install. No idea why, no idea if it’s still happening, I rolled my snapshot back and haven’t tried again.

Has anyone experimented with creating a snapin to enable BitLocker? I wanted to ask before I put the time in.

I plan on writing a batch file to run manage-bde and encrypt the drive, randomly generating necessary keys and storing them in AD. I have a suspicion that I will have trouble doing this because the snapins will be running as SYSTEM (assuming that is still true, I’m fairly new to “new FOG”).

Github 6267 on Ubuntu 14

From the fog_error_6267.log

/opt/fog/snapins/ssl/fog.csr: No such file or directory

I see another posting about the same issue for 6134, but it then goes on to talk about a different issue, so I’m making a new post.

I took a snapshot before I pulled new from github, so I’m going to roll the snapshot back, but could easily recreate again if someone wants me to do further troubleshooting.

@Wayne-Workman Yeah I ended up doing that, I guess as long as my p2ving is what made it angry then there’s nothing to worry about.

FOG build 6152

Random workstations (but not all) have this in their log files this morning:

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 2/8/2016 7:46 AM Client-Info Version: 0.9.10
 2/8/2016 7:46 AM Middleware::Communication URL: http://fog.domain.local/fog/management/other/ssl/srvpublic.crt
 2/8/2016 7:46 AM Data::RSA FOG Server CA cert found
 2/8/2016 7:46 AM Middleware::Authentication Cert OK
 2/8/2016 7:46 AM Middleware::Communication POST URL: http://fog.domain.local/fog/management/index.php?sub=authorize
 2/8/2016 7:46 AM Middleware::Communication Response: Invalid security token
 2/8/2016 7:46 AM Service Sleeping for 120 seconds

Last week things were working fairly well, Friday evening I converted the physical server to a virtual server, and I checked to make sure all the services and what not were running and available, I didn’t make any changes to the server at all. Hitting reset encryption fixes it, so obviously it’s not the end of the world, but I’m not sure that that is what caused it, or if there’s something else going on.

@Wayne-Workman Yeah sorry I thought I had mentioned that earlier. They were fine.

@Wayne-Workman I was able to add a new snapin without doing anything but putting a name in and selecting the storage node. I suppose that’s okay though, yeah?

@Wayne-Workman That seems to have done the trick.

If I select a file to upload, and I select a file that’s already existing, I get the new file uploaded when I update the snapin, but the snapin is configured to use the existing file I selected in the dropdown. That might not be related at all to anything we just did, I just tried it out to see what it’d do.

@Wayne-Workman No, just selecting an existing file. This is what caused it to delete all the snapin files before.

@Wayne-Workman
I made the same change as what you made and now I am getting

FOGFTP: Failed to put file. Remote Path: /opt/fog/snapins/, Local Path: , Error: ftp_put(): Filename cannot be empty

@Tom-Elliott
I posted this in the other thread that I hijacked from IT Solutions, but I’ll post here too to make it easier for you.

I copied my snapin files back over from my old server, and I opened an existing snapin and uploaded a new version and the other snapins files are still there.

I created a new snapin, uploaded a new file, and the other files are still there.

I created a new snapin and selected an existing file and it wiped out all my snapin files.

My guys are saying

“Because after I uploaded the new Chrome, the list of files disappeared and only the one I uploaded was there.
As in, where it says “Snapin File (Exists)” where I can select already uploaded files. It had all the other files listed, then when I made the new spapin and uploaded Chrome, they all vanished, except the new chrome.”

@Tom-Elliott

I copied my snapin files back over from my old server, and I opened an existing snapin and uploaded a new version and the other snapins files are still there.

I created a new snapin, uploaded a new file, and the other files are still there.

I created a new snapin and selected an existing file and it wiped out all my snapin files.

My guys are saying

“Because after I uploaded the new Chrome, the list of files disappeared and only the one I uploaded was there.
As in, where it says “Snapin File (Exists)” where I can select already uploaded files. It had all the other files listed, then when I made the new spapin and uploaded Chrome, they all vanished, except the new chrome.”

@Tom-Elliott I’m going to put my replies into the other guys post over under bugs so as to keep them all in one place.