.32 to 1.2 Now "Task Management" on webserver won't load
-
Did you have to chainload to get systems to boot in 0.32?
Can you try setting the exit type from FOG Configuration->FOG Settings->FOG Boot Settings->FOG_BOOT_EXIT_TYPE The default is sanboot but there’s also exit (which is supposed to drop back directly to bios) and grub.
-
[quote=“Tom Elliott, post: 33938, member: 7271”]Did you have to chainload to get systems to boot in 0.32?
Can you try setting the exit type from FOG Configuration->FOG Settings->FOG Boot Settings->FOG_BOOT_EXIT_TYPE The default is sanboot but there’s also exit (which is supposed to drop back directly to bios) and grub.[/quote]
Hi,
No I never had to use chainloading, I tried EXIT and I got the same behaviour, I tried GRUB and it did load the grub bootloader. So I’ve changed it back to what it was (Default SANBOOT).
The strange thing is that it doesn’t happen every time. Sometimes the computer boots normally. And like I said it doesn’t seem to impact all computers. I have a new 7440 latitude and it boots correctly every time. But the computer that has this intermittent problem is a Latitude E5520. And another person who had this problem was a lenovo desktop M71e! So I can’t see a pattern unless it’s a compatibility problem with certain versions of intel boot agent?
-
[quote=“andyroo54, post: 33942, member: 267”]…it’s a compatibility problem with certain versions of intel boot agent?[/quote]
I think that’s exactly what it is.
That said you could use the provided undionly.kpxe.INTEL file in the /tftpboot folder as your undionly.kpxe. It’s not guaranteed to help, but it might, and I’m not aware of it hurting other systems either.
-
[quote=“Tom Elliott, post: 33943, member: 7271”]I think that’s exactly what it is.
That said you could use the provided undionly.kpxe.INTEL file in the /tftpboot folder as your undionly.kpxe. It’s not guaranteed to help, but it might, and I’m not aware of it hurting other systems either.[/quote]
It’s so strange I booted the E5520 about ten times and it worked 9 times out of 10 on the SANSBOOT mode.
I’ve change it to use kpxe.INTEL and same deal… it works 5 or 6 times them sometimes it just goes to the pxe boot and stays there as above. I noticed there is a maybe error that flashes super fast before it tires to exit iPXE menu. But it’s too fast to catch. Normally it flashes really fast something like “SANSBOOT” but on the times it errors it flashes more text and I noticed the word error.
-
[quote=“andyroo54, post: 33848, member: 267”]we always had this massive delay logging in, it was never a big enough concern to bother looking into from my end but the problem is gone now![/quote]
A little off topic but I have had this problem every single time there’s an update for Fog available
Right now I’m on 1.2 and logging in is instant but on every other version I’ve used (which is all of them since .32), it would take at least 30 seconds to login whenever there was an update available -
@Tom,
I’m also experiencing this issue and the command:
[CODE]udo wget -O /var/www/html/fog/lib/pages/TaskManagementPage.class.php https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/lib/pages/TaskManagementPage.class.php[/CODE]Did not work for me. It downloaded the file but I am still not seeing the TaskManagement page. Any help would be great.
Thanks
-
Have you truncated you snapinTasks and snapinJobs tables?
-
Hello Tom,
Can you provide the steps to do so? Never had to truncate tables in MySql.
-
Actually never mind…I got it.
Below are the truncate steps:
run this at the command prompt[CODE]msyql
[/CODE]
Next screen will look like this:
[CODE]mysql>[/CODE]
then you type the following:
[CODE]use fog
show tables;
truncate table snapinTasks;
truncate table tasks;
truncate table snapinJobs;[/CODE] -
I typically don’t advise truncating the tasks table as you lose all prior tasking records that way.
-
Also, truncating the snapin’s tables means you have to re-add all the snapins to your system.
-
@Tom, I agree, but I’m doing a move from one server to another so wasn’t too concerned with losing prior task records. However, after running the command, the records were still there.
-
The records are stored in the imagingLog’s table, and I only recently as in 1.x.x started copying the records displayed on the home screen from this table, where prior it was pulling from the tasks table entirely.
