Posts made by John Sartoris

@Wayne-Workman

Ok, I didn’t expect that considering Thursday both sites were working fine. I’ll try making the master match storage and see what happens.

Storage - working

/images/Win10BaseR1:
total 18G
-rwxr-xr-x  1 fog  fog   18G Feb  4 15:06 sys.img.000
drwxr-xr-x  2 fog  fog  4.0K Feb  4 15:03 .
-rwxr-xr-x  1 fog  fog  299M Feb  4 15:03 rec.img.000
-rwxr-xr-x  1 fog  fog     0 Feb  4 14:33 d1.original.swapuuids
-rwxr-xr-x  1 fog  fog   259 Feb  4 14:33 d1.original.partitions
-rwxr-xr-x  1 fog  fog    15 Feb  4 14:33 d1.original.fstypes
-rwxr-xr-x  1 fog  fog     2 Feb  4 14:33 d1.fixed_size_partitions
drwxrwxrwx 18 root root 4.0K Feb  4 12:22 ..

Master - not working

/images/Win10BaseR1:
total 18G
drwxrwxrwx 18 fog  root 4.0K Feb  4 15:02 ..
-rwxrwxrwx  1 root root  18G Feb  4 15:02 sys.img.000
drwxrwxrwx  2 root root 4.0K Feb  4 14:33 .
-rwxrwxrwx  1 root root 299M Feb  4 14:33 rec.img.000
-rwxrwxrwx  1 root root   15 Feb  4 14:32 d1.original.fstypes
-rwxrwxrwx  1 root root    0 Feb  4 14:32 d1.original.swapuuids
-rwxrwxrwx  1 root root  259 Feb  4 14:32 d1.original.partitions
-rwxrwxrwx  1 root root    2 Feb  4 14:32 d1.fixed_size_partitions

@Wayne-Workman

I’ve redisabled ufw, added allow rules for good measure. ping works, ssh works, ftp works. Both are running “Ubuntu 12.04.5 LTS”. Storage was installed with 12.04, 6+ months ago after a HD failure. Master was upgraded Friday from 10.04. Ran “apt-get update” and “apt-get upgrade” on both after the 12.04 upgrade. However just tried it again on the master and the 1 package it has an update for is “nfs-kernel-server”.

Master had “1.2.0-4ubuntu4.2” while storage had “1.2.5-3ubuntu3.2” , both now have “1.2.5-3ubuntu3.2”. Problem still existed, after 5 minutes and a manual “sudo service nfs-kernel-server restart” post upgrade , nfs seems to be better, I can now mount the master from storage.

Fog deploy still however still has the same issue when trying to use the local master node. If I point to the cross wan storage node deployment works.

@Wayne-Workman

Ok, I’ve tested mounting the master node exports on the storage node in a temp folder and received a timeout. I repeated in reverse mounting the storage node on the master node in a temp folder without issue. Different mount location of course.

Tried mounting from masternode to masternode, still got the timeout, so it’s not a firewall issues, and it shouldn’t be because I disabled ufw as per the troubleshooting wiki.

showmount shows the exports, any suggestions? I don’t work with NFS much.

# showmount -e 10.2.yyy.xxx
Export list for 10.2.yyy.xxx:
/images/dev *
/images     *
# mount 10.2.xxx.yyy:/images masterimages
mount.nfs: Connection timed out

/etc/exports

/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

# sudo service nfs-kernel-server restart
 * Stopping NFS kernel daemon                                                                                                                                       [ OK ]
 * Unexporting directories for NFS kernel daemon...                                                                                                                 [ OK ]
 * Exporting directories for NFS kernel daemon...                                                                                                                   [ OK ]
 * Starting NFS kernel daemon                                                                                                                                       [ OK ]
# sudo service rpcbind restart
rpcbind: unrecognized service

Is rpcbind required? my second storage node which has been on 12.04 since it was built doesn’t have it either?

Actually it is installed on both…

# apt-cache policy rpcbind
rpcbind:
  Installed: 0.2.0-7ubuntu1.3

Friday I spent some time upgrading our old but well working fog server prepping for our Windows 10 roll out. I upgraded Ubuntu from 10.04 to 12.04, recovered from the apache 2.2 to 2.4 upgrade, installed the new Fog Package, finally got “everything” online, logged in to find another update has been release. I know it’s trunk so it’s going to happen. That’s what I want. Installed 6237 and started testing.

Problem is I can’t deploy an image right now. I’m getting an error “Could not mount images folder (/bin/fog.download)” . As far as I can see the nfs exports are still correct. I found something about creating .mntcheck files in /images and /images/dev, I’ve done that.

Please help, I’m not seeing anything in logs to point me in a direction.

[quote=“UpACreek, post: 38550, member: 24526”]I upped mine to 1536M just to see. I still could not get my login history to load. :([/quote]

I’ve tried the same. I run fog in a ESXi VM. It used to run on a total of 512mb ram and 1 cpu just fine, but trying to resolve this I’ve increased to 2gb ram and Dual CPU. I have 1.72 million records in my user tracking table, going back to the 12-31-2013. I used to have record back to 2011 I think but I purged those out, at least 4 million or so that I deleted.

Looking at the table I wonder if there is a way to ignore a user from the logs. We have a few automatic logon labs that restart frequently. I would like to keep tracking enabled on the machine to log any bypasses of the autologon, but for now I’m disabling tracking on those computers.

I’ve manually tried purging old entries too trying to make the result return fast, but no luck. I’m at 1600+ hosts and and 3600+ users that could be in and out many times a day. I don’t recall having any problems until after the upgrade to 1.2. But I can’t say for sure we would have used the report from 1.0 on. That development was pretty fast and mostly installed over the summer when teachers and students are not around.

[quote=“Junkhacker, post: 34643, member: 21583”]that file should not be there. that report is handled by a class file now
i think you’ve identified a bug. it should be fixed soon[/quote]

Any update on this? Version 1.2 released before this issue and is still current . We used to frequently use this report and are now stuck with less reliable methods.

I’ve been following this post as I too ran into the last step of an image update stalling with *s. I finally received the message about invalid ftp password, and I have since fixed my issue. I had the “2. Fog Configuration > Fog Settings > TFTP Server > FOG_TFTP_FTP_PASSWORD” configured as the fogcrypt’d password. I also had, i’m assuming since I first installed fog, the unix user set to the fogcrypt’d password also. It used to work this way, I don’t know if it should have, but it did.

To fix my issue I had to set the unix user password to the plain text password. The entry in the config page still needs to be fogcrypt’d.

I think I’ve noticed a bug for hosts that have no user login history.

I’ve imported our new laptops this year as the boxes now have mac address barcodes, rather than manually registering 360 of them. When trying to edit the details for these hosts the edit page appears to be visually broken.
[ATTACH]1085[/ATTACH]
At first I thought it was a browser cache issue then I found hosts that worked. I just noticed in the apache error log this message.

[CODE]Call to a member function get() on a non-object in /var/www/fog/lib/pages/HostManagementPage.class.php on line 989[/CODE]

Looks to me like this line works with the user login history, and these hosts don’t have any yet…

After deploying one of these and using the computer, the edit page is fine.

[url=“/_imported_xf_attachments/1/1085_broken host edit page.jpg?:”]broken host edit page.jpg[/url]