@george1421
Increasing PHP-fpm memory did the trick.

Thx for the thinking together.

Hey

Can a user in the fog console change his own password without calling up the list of users?

Because if he calls up the complete list, he can change his password for everyone.

I cannot work with an LDAP, local fog users are needed.

Is this possible via Access Controls?

Tips?

Thanks in advance.

@george1421
Increasing PHP-fpm memory did the trick.

Thx for the thinking together.

For what it’s worth, the export hosts link also gives a HTTP 500 error.

No error logs found, it’s getting a strange problem.

I can’t upgrade do a dev branch. We use fog as a productive rebuilding tool.

@george1421

Nothing in Apache error log, the line in acces log doesn’t explain a lot:

... ] "GET /fog/management/index.php?node=host&sub=list HTTP/1.1" 500 - "http://fog.odl.vdab.net/fog/management/index.php?node=host" "M...

1. Red Hat 7.6
2. 1.5.5
3. 2500+

@Dominique said in List all hosts - HTTP error 500:

No recent messages in www-error.log, last is from August 2018.

[20-Aug-2018 12:14:11 UTC] PHP Warning: phpinfo(): It is not safe to rely on the system’s timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone ‘UTC’ for now, but please set date.timezone to select your timezone. in /var/www/html/fog/management/phpinfo.php on line 3

Memory usages of the server is also OK.
total used free shared buff/cache available
Mem: 4026376 1362544 1570336 28552 1093496 2251816

The memory size in general settings is 2048. Should it be raised?

Thx!

No one?

This is still an issue.

The FOG server’s RAM memory has been expanded to 8. But no luck!

No recent messages in www-error.log, last is from August 2018.

[20-Aug-2018 12:14:11 UTC] PHP Warning: phpinfo(): It is not safe to rely on the system’s timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone ‘UTC’ for now, but please set date.timezone to select your timezone. in /var/www/html/fog/management/phpinfo.php on line 3

Memory usages of the server is also OK.
total used free shared buff/cache available
Mem: 4026376 1362544 1570336 28552 1093496 2251816

The memory size in general settings is 2048. Should it be raised?

Thx!

Hey

When I click in the web interface hosts and then list all hosts, I get a 500 http error.

Access log:
10.121.21.127 - - [11 / Mar / 2019: 20: 22: 46 +0100] “GET /fog/management/index.php?node=host&sub=list HTTP / 1.1” 500 - "http: //fog.odl .vdab.net / fog / management / index.php? node = host “” Mozilla / 5.0 (Windows NT 10.0; Win64; x64) AppleWebKit / 537.36 (KHTML, like Gecko) Chrome / 71.0.3578.98 Safari / 537.36 OPR / 58.0 .3135.79 "

The access log just says 500 error, no detailed error. The error log is empty.

I have already raised the memory size in general settings and php.ini, without result.

Tips?

Thanks in advance!

@Quazz I do the following:

• click Images
• multicast image
• give session name
• client count (12)
• timeout (0)
• choose image
• Start!

The strange thing is, sometimes it reaches the client count. Sometimes not.

We experience problems when sending out an image multicast.

The multicast starts without reaching the client count specified. In the multicast log I see the following:

• the task is created
• image file found
• 4 clients found (however client count in multicast image was 12)
• udp-sender send with a min-receivers of 4
• 4 hosts start multicasting / 8 hosts doing nothing

What can be the reason for this?

Hey

Does anyone have an idea when the disappearance of multicast sessions in FOG 1.5.4 will be solved (see post https://forums.fogproject.org/topic/12180/multicast-sessions-disappearing).

Will this be in the next stable release? If so, when would this come?

For the time being I am dealing with this by increasing the multicast sleeptime. Which of course is not an ideal solution. Since we have a production environment at the company, I can / may not use the working branch.

Thx!