fixed and added.

@Tom-Elliott We only have one group now, so yes.

@Wayne-Workman Timeout is not the same as invalid login though. Though I’ve not tested, I’m pretty sure it will return immediately. Timeout only starts once a valid connection is made.

@Tom-Elliott There is still an apache error happening for updating progress on 8485.

[Fri Jul 08 10:33:12.495255 2016] [:error] [pid 12643] [client 10.32.8.6:34606] PHP Warning: strpos(): Empty needle in /var/www/html/fog/service/progress.php on line 22 [Fri Jul 08 10:33:09.966875 2016] [:error] [pid 12678] [client 10.12.8.35:42580] PHP Warning: array_map(): An error occurred while invoking the map callback in /var/www/html/fog/lib/fog/storagegroup.class.php on line 55 [Fri Jul 08 10:33:09.443653 2016] [:error] [pid 12614] [client 10.12.8.16:50746] PHP Warning: array_map(): An error occurred while invoking the map callback in /var/www/html/fog/lib/fog/storagegroup.class.php on line 55 [Fri Jul 08 10:33:09.376835 2016] [:error] [pid 12640] [client 10.12.8.15:36728] PHP Warning: array_map(): An error occurred while invoking the map callback in /var/www/html/fog/lib/fog/storagegroup.class.php on line 55 [Fri Jul 08 10:33:09.355368 2016] [:error] [pid 12505] [client 10.32.8.6:34604] PHP Warning: strpos(): Empty needle in /var/www/html/fog/service/progress.php on line 22 [Fri Jul 08 10:33:09.284796 2016] [:error] [pid 12629] [client 10.12.8.28:39370] PHP Warning: array_map(): An error occurred while invoking the map callback in /var/www/html/fog/lib/fog/storagegroup.class.php on line 55 [Fri Jul 08 10:33:09.282010 2016] [:error] [pid 12669] [client 10.12.8.21:40094] PHP Warning: array_map(): An error occurred while invoking the map callback in /var/www/html/fog/lib/fog/storagegroup.class.php on line 55 [Fri Jul 08 10:33:08.970103 2016] [:error] [pid 12676] [client 10.12.8.22:35996] PHP Warning: array_map(): An error occurred while invoking the map callback in /var/www/html/fog/lib/fog/storagegroup.class.php on line 55 [Fri Jul 08 10:33:08.708745 2016] [:error] [pid 12463] [client 10.12.8.11:35580] PHP Warning: array_map(): An error occurred while invoking the map callback in /var/www/html/fog/lib/fog/storagegroup.class.php on line 55 [Fri Jul 08 10:33:08.331113 2016] [:error] [pid 12620] [client 10.12.8.18:45480] PHP Warning: array_map(): An error occurred while invoking the map callback in /var/www/html/fog/lib/fog/storagegroup.class.php on line 55

@Sebastian-Roth doubtful. I have no idea what happened.

I built the search plugin for our forums. You are correct that there is no mobile option yet. Currently it just injects the search button into nav bar which doesn’t render on mobile.

It does - in some cases. There’s been a lot of discussion in the forums about RAID and fog - I would suggest you search the forums for “raid” and read through the threads that are under a year old.

The first and easiest thing to try is the kernel argument that specifies raid. I think it’s mdraid=1 but I may be wrong, it’s been a while. Search the forums.

@Joe-Schmitt I’ll do that Monday. 🙂

@Tom-Elliott said:

The canned responses that are available or more of a simple press and send kind of system which might help, but still can leave most of our common questions unanswered.

So what are our common questions that will still be unanswered you think? I guess it’s just a matter of putting all those into the canned responses “template”. I don’t think every user will fill in all the details and we still need to ask questions. But on the other hand a lot of people will happily provide as much information as they can straight from the start if they’d knew what we need to know. So the better questions we have in the “template” the better it will be. Please start adding questions to th OP!

@Wayne-Workman Thanks heaps for keeping in contact with Julian on this!

And that is fixed in latest too.

Bumping this - it would be so nice to have SELinux enabled as a standard configuration.

@Sebastian-Roth Sure. Marking this un-read so I can come back later.

This is untested… But well, what can go wrong?! What do you think about adding the same thing to the registration script if things fail?

Old thread - new news.

Had this error show up when uploading from an EliteBook 8730w with Win10 on it.

While I was digging up the commands in the wiki to fix it, when the laptop rebooted on it’s own (due to error), it began uploading!

How strange?

@Tom-Elliott

Thanks Tom, I figured that might be the case I just wanted to double check.

Probably not a huge priority, but would it be worth adding something to the install script that checks to see if any schema changes are needed, and if not the step about going to the URL to update it is skipped? Or at the very least, add a notice to the step that confirms that going to the URL and not seeing a schema update page is by design if there are no updates, and that you can just continue on with the installer.

I think I can make this tool into a plugin… just a thought…

Ok, together with Jbob I seem to have figured out a working set of libraries (SharpPcap and PacketDotNet) and C# code to send and receive the packets we want. Hopefully we’ll have the first alpha version of a tool ready soon!

OK, after upgrading kingston SSD firmware, changing SATA cable and port, everything seems fine 😉
Thanks !
Matthieu