December 17, 200916 yr Has anyone had this error before: Dec 17 14:16:15 Tower unmenu[1485]: awk: ./unmenu.awk:579: fatal: print to "/inet/tcp/8080/0/0" failed (Connection reset by peer) It cause unmenu not to work. I had to restart the unmenu process. Any ideas?
December 17, 200916 yr Has anyone had this error before: Dec 17 14:16:15 Tower unmenu[1485]: awk: ./unmenu.awk:579: fatal: print to "/inet/tcp/8080/0/0" failed (Connection reset by peer) It cause unmenu not to work. I had to restart the unmenu process. Any ideas? Errors like that are why the "uu" script is a loop that will re-invoke the awk process if it crashes. From what I can see, you lost connectivity to the LAN momentarily. (The error message is slightly misleading, as we don't "print" to the port, but write to it.) Unfortunately, there is no way in "awk" to catch the "fatal" errors. Depending on the error code, unmenu will loop and restart itself. For a few, it will exit. Just re-start it. It is a small miracle it can act as a web-server at all. Joe L.
July 5, 201115 yr I can reproduce this error with the corresponding uu crash quite easily by just clicking through a couple of unMenu options in quick succession. i.e. you click on 'syslog' for example and before the browser responds, you click on another unMenu option. This will typically crash uu requiring a restart. I checked network connectivity while invoking the uu crash and am pretty sure the network is stable. I also don't see any other networking issues during other network operations in including file copies. Seems more to do with uu still processing one HTTP request when a new one comes in?
July 5, 201115 yr I can reproduce this error with the corresponding uu crash quite easily by just clicking through a couple of unMenu options in quick succession. i.e. you click on 'syslog' for example and before the browser responds, you click on another unMenu option. This will typically crash uu requiring a restart. I checked network connectivity while invoking the uu crash and am pretty sure the network is stable. I also don't see any other networking issues during other network operations in including file copies. Seems more to do with uu still processing one HTTP request when a new one comes in? You are correct... and the behavior is because IE closes the connection to the unRAID server if you abort a request... so when unMENU attempts to write to the port, there is nobody listening) As already stated, cannot be caught as "awk" does not include any error handling.
July 5, 201115 yr You are correct... and the behavior is because IE closes the connection to the unRAID server if you abort a request... so when unMENU attempts to write to the port, there is nobody listening) As already stated, cannot be caught as "awk" does not include any error handling. OK, thanks! At least we know and can safely upgrade this behaviour from "bug" to "feature" status.
July 5, 201115 yr Yes, you never double click with unMENU. Always allow the current page to finish loading before clicking something else. Show some patience and restraint and it almost always works great. Peter
July 5, 201115 yr Yes, you never double click with unMENU. Always allow the current page to finish loading before clicking something else. Show some patience and restraint and it almost always works great. Peter Actually, it is a small miracle that it works at all. unMENU was originally intended only as a way to visualize how the unRAID user-interface might be improved... I had no idea it would become so useful. Over time, I expect many of its features to be migrated to version 5.X plugins. Joe L.
July 5, 201115 yr Actually, it is a small miracle that it works at all. unMENU was originally intended only as a way to visualize how the unRAID user-interface might be improved... I had no idea it would become so useful. Over time, I expect many of its features to be migrated to version 5.X plugins. Joe L. Yes, I know. Wasn't V5 being released "fairly soon" also the general concensus at the time? Oh well, it might get here this year. Peter
Archived
This topic is now archived and is closed to further replies.