Ok, I know what I have to do, so bad…
We are agree that compression ratio 7 will produce image smaller that compression ration 1 ?

@Tom-Elliott
ok, so I re-install Mint but I don’t check LVM box ? No other way ?

@george1421

1. git 7009
2. HDD 80GB (I think like you its look like a raw image, half compressed)
3. LVM partition and ext4 file format

Hi,

I’m not sure it’s a bug, but I asked some colleagues with fog 1.2 and they don’t have this problem.
I prepared a linux machine based on Mint 17.3 Xfce distribution, which use less than 7GB space on HDD :

ecole@ecole-desktop ~ $ df
Sys. de fichiers blocs de 1K Utilisé Disponible Uti% Monté sur
udev                  492232       4     492228   1% /dev
tmpfs                 101428    1268     100160   2% /run
/dev/dm-0           75519088 5908904   65750936   9% /
none                       4       0          4   0% /sys/fs/cgroup
none                    5120       0       5120   0% /run/lock
none                  507136      76     507060   1% /run/shm
none                  102400      24     102376   1% /run/user
/dev/sda1              49320   47834          0 100% /boot

I uploaded image, but image is more than 30GB !

root@FOG:/images$ du -h Mint2/
31G     Mint2/

Here is my image parameters :

Thanks

@Tom-Elliott Ok I understood… Could it become an option which can be activated if needed in fog settings ?

@Tom-Elliott After updating to svn 6799, it seems ok, no new line in history table

I saw into table that each computer update each minute, that’s why there are so many lines…
But I’m pretty sure database and history table was much smaller before latest svn update…

Hi,

When I looked on fog database size, I found it was much bigger than before (150Mo vs 2Mo usually).
In fact, history table is around 146Mo, but I don’t know why it grows so quickly…
I truncate it 10 minutes ago and there’s already 3000 lines which look like this :

[2016-03-17 14:02:54] Host ID: 28 NAME: MATT has been successfully updated.

Any reason ?

@Wayne-Workman ok ! That was the trick ! But why…
Solved for me
Thanks guys

@Sebastian-Roth I check this, password in /opt/fog/.fogsettings was different.
Password for fog user, storage node and FOG_TFTP_FTP_PASSWORD areidentical.
I change password in /opt/fog/.fogsettings to match with other but no changes, always same error

I saw this “bug” few days ago, snapin didn’t work any more, bu I don’t understand why it has changed… I I make no change for this.

I’ll take a look tomorrow

Hi,

I just deploy a host, and it didn’t want to deploy snapin, any idea ? Thanks

-----------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 09/03/2016 14:48 Client-Info Version: 0.9.11
 09/03/2016 14:48 SnapinClient Running...
 09/03/2016 14:48 Middleware::Communication URL: http://192.168.10.60/fog/service/servicemodule-active.php?moduleid=snapinclient&mac=00:1C:C0:D4:BD:F8|&newService=1
 09/03/2016 14:48 Middleware::Communication Response: Success
 09/03/2016 14:48 Middleware::Communication URL: http://192.168.10.60/fog/service/snapins.checkin.php?mac=00:1C:C0:D4:BD:F8|&newService=1
 09/03/2016 14:48 Middleware::Communication Unknown Response: Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 104, Message: ftp_login(): Login incorrect.
------------------------------------------------------------------------------

Good question ^^
I can tell you this on monday !

It’s not a big deal, but when I approve mac address on host page

it gives me a black page…

After refreshing page it’s ok

and I haven’t got this problem if I approve pending MAC on home page or report management page

Thanks for fixing it

Same problem for me yesteray after upgrade, so I restore my last backup from friday, and after new upgrade everything was ok

@Tom-Elliott Yes, it’s ok with 6413

@Tom-Elliott I use 6411 trunk, I’ll try to update

@Tom-Elliott ok, I’ve got this :

root@FOG:/opt/fog/snapins/ssl$ ls
total 20
drwxr-xr-x 3 fog www-data 4096 fevr. 24 18:05 .
drwxrwxr-x 3 fog www-data 4096 fevr. 24 18:05 ..
drwxr-xr-x 2 fog www-data 4096 oct.  10 08:52 CA
-rw-r--r-- 1 fog www-data 1590 aout  27 10:36 fog.csr
-rw-r--r-- 1 fog www-data 3243 aout  27 10:36 .srvprivate.key
root@FOG:/opt/fog/snapins/ssl$ cd CA
root@FOG:/opt/fog/snapins/ssl/CA$ ls
total 20
drwxr-xr-x 2 fog www-data 4096 oct.  10 08:52 .
drwxr-xr-x 3 fog www-data 4096 fevr. 24 18:05 ..
-rw-r--r-- 1 fog www-data 3243 aout  27 10:36 .fogCA.key
-rw-r--r-- 1 fog www-data 1797 aout  27 10:36 .fogCA.pem
-rw-r--r-- 1 fog www-data   17 fevr. 24 18:05 .srl
root@FOG:/opt/fog/snapins/ssl/CA$

But still no communication between hosts and server…

@ITSolutions It worked on monday, but I updated trunk this morning, and after that I had this problem.
In opt/fog/snapinq there is no CA folder, but there is ssl folder with CA folder inside
And no /opt/fog/ssl folder…

Hi,

I deployed 2 hosts today, and both of them have this error :

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 24/02/2016 18:14 Client-Info Version: 0.9.11
 24/02/2016 18:14 Middleware::Communication URL: http://192.168.10.60/fog/management/other/ssl/srvpublic.crt
 24/02/2016 18:14 Data::RSA FOG Server CA cert found
 24/02/2016 18:14 Middleware::Authentication Cert OK
 24/02/2016 18:14 Middleware::Communication POST URL: http://192.168.10.60/fog/management/index.php?sub=authorize
 24/02/2016 18:14 Middleware::Communication Unknown Response: Private key not found
 24/02/2016 18:14 Service Sleeping for 120 seconds
 24/02/2016 18:16 Bus Registering ParseBus in channel Power
 24/02/2016 18:16 Bus Became bus client
 24/02/2016 18:16 Bus Registering OnNotification in channel Notification
 24/02/2016 18:16 Bus Registering OnUpdate in channel Update

Any idea ?

Thanks
Matthieu

@Sebastian-Roth ok, and thanks again so much for your help.
Do you think we can mark this topic as resolved, or we are waiting for a fix from HP / Insyde ?