Topics created by Wayne Workman

There’s now way to control the flow of how a form get’s processed, unfortunately. The Data get’s uploaded then the “variables” are suitable to test. This includes files (regardless of size). That said, i have included a jquery method that will test the variables before they go to be “processed” and if the name is not set, it will no longer submit, wait, then test. It will immediately prevent the submit action and point you to the name not being filled out (or using invalid characters).

I’ve solved this for now as the other thread is also reporting as solved since switching to ksort from asort.

@Tom-Elliott said in FOS checkin time:

The fact that you had a capture going (writing), and 6 deploy’s going (6 different reads) was a portion of what the load by the server is being caused from.

That wasn’t the case yesterday.

Yesterday, no captures were going. 3 computers were imaging, 12 were waiting in queue to image. The 3 were imaging from a remote server, not even the main server. And the main server’s CPU was maxed out.

fixed and added.

Just remembered Tom.
I’ll do a pull request for the text when I can.

@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 Trunk 8485 appears to be functional for imaging with the location plugin - confirmed at two sites so far. I assume the rest are good.

This already exists. It’s the fog log files that show the storage node name as part of the file name.

@Wayne-Workman woot. I think the other thread that was similar to this should be updated as well. Sorry it took so long to figure out at any rate.

@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

Tom says he added code for node replication to iterate through each group it belongs to.

However I’ve already done an overhaul to go down to just one storage group and I THINK replication is working.

When the dust clears, we will know.

Confirmed fixed, the client is now showing in the logs the scheduled power task.

I don’t know how this is a bug.

Things are stored as they were created. The checks are there to prevent people from stealing already in use names. This is intentional. If you really need it case sensitive as a “pretty” factor, delete it and recreate it using the proper case, or manually edit the DB so it is displayed how you prefer.

wait… never mind. I’m stupid sometimes.

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.

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

This is fixed - just confirmed it.