The MyLDAP plugin only update the typeUser field from 990 to 0. Then the solution is easy in this case, we can change the LDAP plugin and add a checkbox to do the users persistent or not.

@Tom-Elliott said in New plugin: MyLDAP. LDAP Extension Plugin:

The reason this is not added to the current ldap plugin is because:

1. If you persist the user, when your AD Password is reset, how does the GUI know of the change? (Yes I know this is already addressed, but this is more so people understand the thought processes.)

The MyLDAP plugin takes it in account and after the validation in the AD o LDAP server, update the password in the FOG DB. Well, I think that save the password in the DB is a little security hole, if you know the encryption mode, you can decrypt the password that is saved in DB. I porpose to not save it in the DB with the users created by LDAP plugin and only save the “local users”, the users that you create from the webUI.

Hi Fogers!

I have developed a new plugin: MyLDAP plugin.

Description: This plugin is an extension of LDAP plugin. MyLDAP plugin does persistent the users who are created by LDAP plugin. Useful when you use AccessControl Plugin or Site Plugin.

The LDAP plugin creates users on the fly, these users are erased from the database when the user logoffs from the webUI. If you use the AccessControl plugin or site plugin, the relation user-accesscontrol or user-site will lose when the user logoffs because the user entry in the DB is erased. MyLDAP plugin does the user persistent in the DB. If the user changes his/her password in the LDAP server or in AD, the password will be updated during the validation process.

Dependencies: LDAP plugin

Sorry Tom I forget do it. Yes, If I increase the maximum execution time to 60 seconds, the report runs well

Hi Tom,

Finally works fine under ubuntu 14.04

sudo rm /etc/apt/sources.list.d/mono-xamarin.list
sudo apt-get autoremove
sudo apt-get update
sudo apt-get install mono-complete
Install the client

With these instructions the client woks fine. Thanks!!

I wiil try it but I always use a Ubuntu/Centos fresh install

Yes I have reseted the encryption. I will do more test about this.

The date in the server and in the client is the same

Server

• FOG Version: 6070
• OS: RedHat 7.3

Client

• Service Version: 0.11.12
• OS: Linux

Description

I try to install the linux client under different distros (Ubuntu 14.04, Ubuntu 16.04 and Centos 7) and doesn’t work well.

 29/05/2017 15:27 Main Bootstrapping Zazzles
 29/05/2017 15:27 Controller Initialize
 29/05/2017 15:27 Controller Start

 29/05/2017 15:27 Service Starting service
 29/05/2017 15:27 Bus Became bus server
 29/05/2017 15:27 Bus Emmiting message on channel: Status
 29/05/2017 15:27 Service Invoking early JIT compilation on needed binaries

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 29/05/2017 15:27 Client-Info Version: 0.11.12
 29/05/2017 15:27 Client-Info OS:      Linux
 29/05/2017 15:27 Middleware::Authentication Waiting for authentication timeout to pass
 29/05/2017 15:27 Middleware::Communication Download: http://fog.ehu.eus/fog/management/other/ssl/srvpublic.crt
 29/05/2017 15:27 Middleware::Authentication ERROR: Could not authenticate
 29/05/2017 15:27 Middleware::Authentication ERROR: Value cannot be null.
Parameter name: authority

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 29/05/2017 15:27 Client-Info Version: 0.11.12
 29/05/2017 15:27 Client-Info OS:      Linux
 29/05/2017 15:27 Middleware::Authentication Waiting for authentication timeout to pass
 29/05/2017 15:29 Middleware::Communication Download: http://fog.ehu.eus/fog/management/other/ssl/srvpublic.crt
 29/05/2017 15:29 Middleware::Authentication ERROR: Could not authenticate
 29/05/2017 15:29 Middleware::Authentication ERROR: Value cannot be null.
Parameter name: authority

I read the Certificate is not from FOG CA post but nothing. Anyone more has the same problem?

As a suggetion, perhaps if you could config an interval time … I don’t need all log, only the last ones In this way we can optimize the resources.

I have increased the memory and the imaging log report works fine

But the snaping log follows with the same error:

PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 1023, referer: http://fog.ehu.eus/fog/management/index.php?node=report&sub=file&f=aW1hZ2luZyBsb2c=

Works fine!!!

Server

• FOG Version: 1.4.0 (SVN version 6070)
• OS: RedHat 7.3

Client

• Service Version: 0.11.12
• OS: Windows

Browser

• Version: Firefox 53.0.2

Description

When I try to see Imaging Log Report the page is blank and in the apache error_log file appears:

PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32 bytes) in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 834, referer: http://fog.ehu.eus/fog/management/index.php?node=report

With the the others reports works fine except with snaping log that the error is different:

PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 1073, referer: http://fog.ehu.eus/fog/management/index.php?node=report

The server has 4 cores and 4 GB RAM.

Hello Tom,

I have updated the version and the problem follows

Hello!!
I try the multicast image (I don’t use it until now) and the behaviour is the same. In the active multicast task page doesn’t update the status.

@Tom-Elliott said in Multicast task status doesn t update:

Is the task running?

Yes, of course, and downloading

Thank you

@Quazz said in Multicast task status doesn t update:

Which method do you use to launch the multitask task? Group or image?

Group

The situation:

I send a multicast task to 30 hosts and the image has 3 partitions.
For several causes someones of these hosts doesn’t power on (the net wire is not connected, the WOL packet doen’t reach to the host …). At last 25 hosts are power on and 5 power off. The task begins and, after timeout, the download process begins in 25 hosts, you go to the classroom and … Oh my God!!! I need all PC for the next hour!!! You can not stop the task because has downloaded the middle. The solution would be easy, cancel the five ones, and create a new multicast task with these five.

With the actual behaviour you can do this.

Please, close the ticket I can not repeat the situation.
I try several times and now works fine

Server

• FOG Version: 1.4.0
• OS: RedHat 7.3

Client

• Service Version: 0.11.12
• OS: Windows

Description

when you launch a mulitcast task, his status doesn’t update in the Active Multicast task page. Always appears like “Queued”.