Posts made by Scott B

@Tom-Elliott said in Invalid host certificate:

Please update to latest.

Looking better…

------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 4/27/2016 3:24 PM Client-Info Version: 0.9.12
 4/27/2016 3:24 PM PrinterManager Running...
 4/27/2016 3:24 PM Middleware::Communication URL: http://fog-server/fog/service/servicemodule-active.php?moduleid=printermanager&mac=78:AC:C0:98:3A:FA|&newService=1
 4/27/2016 3:24 PM Middleware::Communication Response: Success
 4/27/2016 3:24 PM Middleware::Communication URL: http://fog-server/fog/service/Printers.php?mac=78:AC:C0:98:3A:FA|&newService=1
 4/27/2016 3:24 PM Middleware::Communication Unknown Response: 
 4/27/2016 3:24 PM Service ERROR: Object reference not set to an instance of an object.
------------------------------------------------------------------------------

This started showing up only in the past couple days. I get an invalid host certificate error in the fog.log and thus things like printer installs do not happen. I’ve tired removing and reinstalling the fog service, manually installing the srvpublic.crt, and resetting encryption on that host. Any suggestions?

4/27/2016 2:53 PM Middleware::Communication Response: Invalid host certificate
4/27/2016 2:53 PM Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
4/27/2016 2:53 PM Data::RSA FOG Server CA cert found
4/27/2016 2:53 PM Middleware::Authentication Cert OK
4/27/2016 2:53 PM Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
4/27/2016 2:53 PM Middleware::Communication Response: Success
4/27/2016 2:53 PM Middleware::Authentication Authenticated
4/27/2016 2:53 PM Middleware::Communication URL: http://fog-server/fog/service/jobs.php?mac=78:AC:C0:98:3A:FA|&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&newService=1&n

@Wayne-Workman said in Printer management Windows 7:

@Wayne-Workman said in Printer management Windows 7:

@Tom-Elliott said:

it’s supplying the location where the Client will get its driver from.

I would like to put drivers in a share folder.

Coming back to this old thread because I’m now trying to deploy a very difficult to deploy printer via FOG, and I’ve made a basic startup script to keep a local drivers folder updated.

Basically, whenever you want the folder updated on all the systems, you just put in a new text file with a current date for the name (file is empty), and then update the script to look for the new file.

IF NOT EXIST "%SystemDrive%\print_drivers\4-13-2016.txt" (
rmdir %SystemDrive%\print_drivers /s /q
xcopy "\\x.x.x.x\YourShare\print_drivers\*.*" "%SystemDrive%\print_drivers" /y /d /e /c /i /f /h /k /v /s
)

How varied are your makes and models of printers? I wrote a batch file that will determine if you are Win7 or 10, x32 or x64 and copy all the drivers local. FOG then looks to that local path. It looks similar to the one you posted.

Same issue here. When looking at the workstations fog.log logs I says all the services are disabled globally. Also, are you able to deploy an image? I get the error below, but its there.

As @Scott-Adams said above reboots and restarts of the services do not help.

Ubuntu 14.04.4 LTS
SVN 7324

With a lot of help from @Sebastian-Roth we did track down the issue. Someone must have been in our DHCP server and changed the case of the undionly.kpxe to all caps… thus not finding the file. Sometimes is those simple things you just don’t think to look for. Thanks again for your help Sebastian!

@Sebastian-Roth said:

@Scott-B said:

Mar 24 08:44:49 FOG in.tftpd[31921]: tftp: client does not accept options

You can safely ignore this. It’s just a notice and does not prevent the client from downloading binaries via TFTP! I guess this message in the log came up when you tried tftp from the server console, right?? Please try again from the server and remote and see when you get the message in the logs.

Other than that I am kind of lost with this. Have you double/triple checked the IP addresses? Are you able to ping both ways (client which you test tftp from and FOG server)??

I was able to tftp a file from the console, I was trailing the syslog at the time and did not see the message again. I can ping both ways without issue.

/var/log/syslog show the messages below.

Mar 24 07:52:26 FOG in.tftpd[29283]: tftp: client does not accept options
Mar 24 08:03:59 FOG in.tftpd[29827]: tftp: client does not accept options
Mar 24 08:09:01 FOG CRON[30159]: (root) CMD (  [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Mar 24 08:16:10 FOG in.tftpd[30432]: tftp: client does not accept options
Mar 24 08:17:01 FOG CRON[30490]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 24 08:39:01 FOG CRON[31690]: (root) CMD (  [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Mar 24 08:44:49 FOG in.tftpd[31921]: tftp: client does not accept options
Mar 24 09:01:08 FOG kernel: [73741.076609] ip_tables: (C) 2000-2006 Netfilter Core Team
Mar 24 09:09:01 FOG CRON[911]: (root) CMD (  [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Mar 24 09:17:01 FOG CRON[1629]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

I also checked the firewall

root@FOG:~# ufw status
Status: inactive

@Sebastian-Roth said:

My guess it’s firewall… iptables -L -n -v

root@FOG:~# iptables -L -n -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

@Quazz said:

@Scott-B What does your /etc/default/tftpd-hpa file look like?

# /etc/default/tftpd-hpa
# FOG Modified version
TFTP_USERNAME="root"
TFTP_DIRECTORY="/tftpboot"
TFTP_ADDRESS=":69"
TFTP_OPTIONS="-s"

@Quazz said:

@Scott-B Could you check on a non-VM machine if it works? I’m not overly familiar with VM but I do know VM’s can be weird with PXE sometimes, they’re particularly picky with what network adapter will work.

I’ve tried on both physical and vm devices.

@Sebastian-Roth said:

Maybe you upgraded the system as well. Possibly enabling the firewall??

I can tftp a file directly from the server console so its at least running. The only firewall on the system is ufw (Uncomplicated Firewall) but its disabled on start and is not running on the system.

@Tom-Elliott

I get a “timeout occurred. connect request failed.” when I try to send a file manually. Same if I try to get a file as well.

@Tom-Elliott said:

It’s most likely nothing to do with FOG as it’s not even getting to the point of requesting a file, from what I can see. That or the FOG Server doesn’t have tftp running?

tftpd-hpa service shows running. I tried restarting it as well. Checked in fog’s web gui and the user and password listed for fog tftp are correct.

When booting pxe I’ve started getting a file not found message. No changes have been made to the DHCP servers that I’m aware of, and only an SVN update to FOG (currently 6911 on Ubuntu 14.04) and I see undionly.kpxe in the tftpboot directory. Rights to undionly.kpxe are 664. Owner fog:root. Any ideas?

@Sebastian-Roth said:

Marking this solved for now as we didn’t hear back from anyone. If you have printer issues please follow the link Wayne posted below. If you still think there is an issue within FOG please let us know!

I apologize for the delay, been swamped. It does seem the issue has been resolved. I have not seen it after the past several SVNs. Thank you very much for your help.

Is there anything specifically special about imaging a linux based device? I have some old netbooks that are running Puppy Linux. I created an image, and a 2nd one to test, that uses part clone. The image seems to capture without a problem as well as deploy, but upon rebooting I only ever get the grub> loader. I’ve tried making and remaking the image a few times and using a different image in fog to the same result. Is there something I should do before uploading a linux image?

On Ubuntu 14.04

Same issue here as of SVN 6627.

@Tom-Elliott said:

@Scott-B Is it possible that the links are causing weird things?

Can you delete all webroot paths for fog?

rm -rf /var/www/fog
rm -rf /var/www/html/fog

Then rerun the fog installer?

Thanks Tom, that did the trick.

I changed a few things around and ran both on the primary and the storage node. Exact same commands. Storage node updated. Primary still on 6179.

Install:

cd /root
mkdir fogsvn
cd fogsvn
mkdir trunk
cd trunk
svn checkout https://svn.code.sf.net/p/freeghost/code/trunk /root/fogsvn/trunk
cd /root/fogsvn/trunk/bin
./installfog.sh

Update:

cd /root/fogsvn/trunk
svn up
cd bin
./installfog.sh

I don’t get why 1 updates fine and the other doesn’t when the same commands are used. Could me something little I’m just not seeing. If move to the trunk folder and do a svn up, both say “At revision 4792”.