Fog 1.1.0 multicast sits at "Starting to restore image (-) to device (/dev/sda1)
-
ok i went to SVN 1813 but i still had same problem.
i will do a full reinstall of ubuntu server and then go to the latest svn and see if that fixes it
-
Hi, first of all I’d like to say I’m a new but happy user of Fog.
I’ve got the same Multicast problem with both of my networks :- the test one with a VMWare Debian 7 machine
- the real physical one with a FOGserver on Debian 7 too.
[CODE][06-13-14 1:51:09 pm] | Task (4) VMxp is new!
[06-13-14 1:51:09 pm] | Task (4) VMxp image file found.
[06-13-14 1:51:09 pm] | Task (4) VMxp client(s) found.
[06-13-14 1:51:09 pm] | Task (4) VMxp sending on base port: 64916
[06-13-14 1:51:09 pm] CMD: cat “/images/test”|/usr/local/sbin/udp-sender --min-receivers 2 --portbase 64916 --interface eth0 --full-duplex --ttl 32 --nokbd;
[06-13-14 1:51:09 pm] | Task (4) VMxp has started.
[06-13-14 1:51:19 pm] | Task (4) VMxp is already running PID 6647
[06-13-14 1:51:29 pm] | Task (4) VMxp is already running PID 6647
[06-13-14 1:51:39 pm] | Task (4) VMxp is already running PID 6647
[/CODE]I hope we’ll find the answer
Best regards to the developpers
-
Please update to 1817. I figured out a WHOLE lot of things last night and really do need a GOOD test from real world environments. I tested at home two a two client group and all worked properly, but a realworld test would be best.
The message “Already running PID” is accurate though.
Thank you, -
I uploaded svn 1817 and then try to update, but I’m stuck in the database update/install process.
When I click on update, I’ve got a blank screen( no error ) with the tittle
[SIZE=6][B][FONT=Ubuntu][CENTER][SIZE=32px][COLOR=#666666][SIZE=4]Database Schema Installer / Updater[/SIZE][/COLOR][/SIZE][/CENTER][/FONT][/B][/SIZE]. Did I miss something ?
-
[quote=“Tom Elliott, post: 30139, member: 7271”]Please update to 1817. I figured out a WHOLE lot of things last night and really do need a GOOD test from real world environments. I tested at home two a two client group and all worked properly, but a realworld test would be best.
The message “Already running PID” is accurate though.
Thank you,[/quote]I had the problem described above and just updated to 1817 - all seems to be working fine here on 20 PCs
Many Thanks!
-
I updated to 1818 and It’s still sitting at the “Starting to restore image (-) to device (/dev/sda1)” screen
I’m using Ubuntu 13.10
Any guess on things to try?
-
[quote=“Flavalf, post: 30153, member: 24625”]I uploaded svn 1817 and then try to update, but I’m stuck in the database update/install process.
When I click on update, I’ve got a blank screen( no error ) with the tittle[CENTER][SIZE=6][FONT=Ubuntu][B][SIZE=32px][COLOR=#666666][SIZE=4]Database Schema Installer / Updater[/SIZE][/COLOR][/SIZE][/B][/FONT][/SIZE][/CENTER]
. Did I miss something ?[/quote]
Restart MySql. I got this a bunch until I removed the root MySql password.
-
[quote=“Michael Mullins, post: 30162, member: 17924”]Restart MySql. I got this a bunch until I removed the root MySql password.[/quote]
I’d say cancel the tasks and clear your tables.
[code]truncate table multicastSessions;
truncate table multicastSessionsAssociations;[/code]Recreate your multicast task and restart those clients
all should work. -
excuse me for my ignorance, but it gives a error saying that i need to give a size when i try to truncate.
-
Login to the mysql instance and use the database fog
[code]mysql -u root [-p IF YOU SET PASSWORD] fog
truncate table mutlicastSessions;
truncate table multicastSessionsAssoc;
exit[/code] -
Hmm… That did’t work… but it killed mysql…
-
Ok, Reinstall Unbuntu 13.10 and installed Fog v1.1.1 and still hangs at the same place on multicast.
-
If you had to “restart” mysql because it “killed mysql” you’ll most likely need to restart the services.
Here’s the process I imagine:
[code]sudo service mysql restart &&
sudo service apache2 restart &&
sudo service FOGMulticastManager restart &&
sudo service FOGImageReplicator restart &&
sudo service FOGScheduler restart[/code]The \ just allows you to keep adding to the current command. The && only starts the next command if the previous command completes successfully. If it doesn’t complete successfully it will not run the next, or any other of the commands in sequence. This can help you find out an issue.
-
If all restarts and returns properly, you’ll most likely have to restart the clients as the udp-sender commands will start, but there was no communication between the clients and the server before. Just restart the clients and all should start properly.
-
No, I started fresh. I wiped and reinstalled Unbuntu 13.10 and then Installed Fog v 1.1.1. Then Uploaded an image. Test pushed the image to a single machine and then tried a Multicast of 2 Machines. It’s still hanging at the “Starting to restore image” part.
-
Can you please try the steps I just gave?
-
Ok, Tried what you asked. Everything restarted without problems. Tried Multicast again. Still have the problem.
-
Thanks for your Help Tom. I’m headed home for the weekend. Hopefully we can figure out an answer when I get back to work on Monday.
Have a Great Weekend.
-
Based on the information, does your network allow UDP traffic to pass?
-
im in the same boat as michael. i reinstalled ubuntu 12.04 lts server. installed fog svn 1820. normal unicast works fine, but the group multicast with more than 1 member doesnt work.
here is the multicast.log.udpcast.6 (in this case its a 6) log:Udp-sender 20120424
Using mcast address 234.1.1.242
UDP sender for (stdin) at 10.1.1.242 on eth0
Broadcasting control to 224.0.0.1
New connection from 10.103.50.144 (#0) 00000009
New connection from 10.103.50.151 (#1) 00000009
Starting transfer: 00000009
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000it just keeps going.
when i multicast to a group with one member, it works. here is the multicast.log.udpcast.8:
Udp-sender 20120424
Using mcast address 234.1.1.242
UDP sender for (stdin) at 10.1.1.242 on eth0
Broadcasting control to 224.0.0.1
New connection from 10.103.50.144 (#0) 00000009
Starting transfer: 00000009
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=1220
bytes= 4 729 088 re-xmits=0000029 ( 0.8%) slice=0112 - 0
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=1207
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=1311
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=1161
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=1223
bytes= 21 851 648 re-xmits=0002455 ( 16.3%) slice=0112 - 0
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=1238
bytes= 29 516 032 re-xmits=0003904 ( 19.2%) slice=0112 - 0
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=921
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=1151
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=1173
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=1161
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=1155
So i notice that for both groups, everthing is the same until Timeout notAnswered=
For the group with 1 member, its:
Timeout notAnswered=[0] notReady=[0] nrAns=0 nrRead=0 nrPart=1 avg=1220
For the group with 2 members, its:
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
The group with 2 members, that message keeps on repeating forever, and the client doesnt show any change.
The group with 1 member, every so often will update with a:
bytes= 29 516 032 re-xmits=0003904 ( 19.2%) slice=0112 - 0
If everyone else is getting it to work, then it makes me think the switches on my side are at fault. In which case shame on me for posting this. And shame on my colleagues for messing around with the switches.
Please let me know if anyone else is having this issue. I’ll work on my end and post what i found. Im hoping its just a switch where multicast isnt enabled.
