Topics created by jamesb

You might fix this by truncating the snapins db there is a post about it when first installing svn.

That worked. Thank you Tom.

Here is exactly what we used to test the connections:
root@fogVM:/images/DellOptiplex3020syspreptest# udp-sender --file /opt/fog/log/multicast.log --ttl 32 --mcast-data-address 239.168.1.1 --min-receivers 2
Udp-sender 20120424
Using full duplex mode
UDP sender for /opt/fog/log/multicast.log at 172.28.2.21 on eth0
Broadcasting control to 224.0.0.1
New connection from 172.28.16.36 (#0) 00000009
Ready. Press any key to start sending data.
New connection from 172.28.16.49 (#1) 00000009
Ready. Press any key to start sending data.
Starting transfer: 00000009
bytes= 2 200 re-xmits=0000001 ( 50.0%) slice=0112 - 0
Transfer complete.
Disconnecting #0 (172.28.16.36)
Disconnecting #1 (172.28.16.49)

Here is the one for the image:
root@fogVM:/images/DellOptiplex3020syspreptest# gunzip -c “/images/DellOptiplex3020syspreptest/d1p1.img” | /usr/local/sbin/udp-sender --min-receivers 2 --mcast-data-address 239.168.1.1 --portbase 9000 --interface 172.28.2.21 --full-duplex --ttl 32
Udp-sender 20120424
UDP sender for (stdin) at 172.28.2.21 on eth0
Broadcasting control to 224.0.0.1
New connection from 172.28.16.36 (#0) 00000009
Ready. Press any key to start sending data.
New connection from 172.28.16.49 (#1) 00000009
Ready. Press any key to start sending data.
Starting transfer: 00000009
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=6696
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=6696
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=6696
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=6696

user access controls is a feature that is currently under development, but it is unknown how long it will take to complete.

Hello people!

Recently I had a similar problem. My FOG solution is:

FOG version 1.2.0 revision 3246 Ubuntu Desktop 13.10 i386

Working with Hosts Management section, creating a host, erasing this host and again creating the host with same MAC I had the trouble that FOG said me that this hostname already exists. In the Host Management section did not appear the host.

The solution is like Tom says. Thank you Tom!!

For me, deleting the registers in fog database with the [I]wrong[/I] host ([I]wrong[/I] means the created, then deleted and then tried to create) in [I]host[/I] and [I]hostMAC[/I] table was the solution.

I searched how to manipulate fog database. I used phpMyAdmin (searching directly with Ubuntu Software Center). Then I configure to get access to the fog database (I used blank password in mysql). Edit /etc/phpmyadmin/config.inc.php
[INDENT=1]Uncomment this line:[/INDENT]
[INDENT=1][COLOR=#3366ff][SIZE=4]$cfg[‘Servers’][$i][‘AllowNoPassword’] = TRUE;[/SIZE][/COLOR][/INDENT]
[INDENT=1]Save file.[/INDENT] Finally, search the tables [I]host[/I] and [I]hostMAC[/I] and delete the [I]wrong[/I] host registers.

I hope it helps. See you,

T. Capablo.

Last logged in user hasn’t just been talked about but has existed since I believe 0.29. It even tells you the times they login and log out. Knowing a system is powered on could be performed by enabling host lookup and allowing the systems firewall to respond to icmp requests.

Could you provide more details? What version of FOG are you running and could you upload the fog.log file?

[url]http://fogproject.org/wiki/index.php/Managing_FOG#Snap-ins[/url]

Just added that to the wiki sorry for not having that specified.

to expand on what Tom said and clarify what kind of time frame we’re talking about, 1.3.0 is our next release point (weeks to months, expected), and 1.4.0 would be the next major release point (months to years away).

@cotec , can you post this to a new topic, otherwise it will get buried.