communication failure

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • This is a result of the filesystem command that engined (written in php) not completing in time that extjs (javascript) allows. Is the drive failing or being heavily used? Have a look at this code
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Currently I'm formatting /dev/sdc.

      Source Code

      1. root@omvnas:~# ps -aux | grep mkfs.ext4
      2. root 1528 0.0 0.0 12728 2160 pts/0 S+ 18:03 0:00 grep mkfs.ext4
      3. root 17905 0.5 0.0 23800 6652 ? D 17:05 0:20 mkfs.ext4 -b 4096 -m 0 -E lazy_itable_init=0,lazy_journal_init=0 -O 64bit -L sr2 /dev/sdc1
      There is no other reason for communication error.
    • Maybe the following code throws exception, and doesn't return any info

      Source Code

      1. throw new \OMV\ExecException($cmd->getCommandLine(), $output,
      2. $exitStatus);

      I don't find any "communication failure" string in the file above.

      The only string I found:
      github.com/openmediavault/open…nication+failure%22&type=

      Source Code

      1. openmediavault (3.0.20) stable; urgency=low
      2. * Update locales.
      3. * Various improvements and bugfixes.
      4. * Mantis 0001522: Communication failure popup clicking
    • klorinczi wrote:

      Currently I'm formatting /dev/sdc.

      There is no other reason for communication error.
      High load on the system can cause the problem. What kind of system?

      klorinczi wrote:

      I don't find any "communication failure" string in the file above.
      The failure comes from the javascript side. I just pointed to the php code that isn't returning info because the command hasn't completed.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      klorinczi wrote:

      Currently I'm formatting /dev/sdc.

      There is no other reason for communication error.
      High load on the system can cause the problem. What kind of system?

      klorinczi wrote:

      I don't find any "communication failure" string in the file above.
      The failure comes from the javascript side. I just pointed to the php code that isn't returning info because the command hasn't completed.
      System is an MSI server motherboard with 16 Gb memory, dual AMD OPTERON processor.
      It is spare now, so nothing memory or processor intensive tasks are running on it.

      Should not have performance problems.
      The problem clearly comes from OMV 3.

      The problem is that javascript doesn't give any information, what script was executed.
      Is debug mode implemented in OMV at all?

      Sent with Tapatalk from my SM-N9005
    • I have the same problem. Please see my posts in this thread.

      I get it when a ZFS scrub is running in the background, which generates a heavy disk load. Or when the drives are in standby and need to be started first. There are several other threads where people report this issue, when they are doing disk related tasks (File system actions, S.M.A.R.T. a.s.o)

      I have filed a bug report at bugtracker some days ago, but no reply so far (Absolutely no criticism!). Therefore I think there is no simple solution for this behavior.
      OMV 3.0.90 (Gray style)
      ASRock Rack C2550D4I - 16GB ECC - 6x WD RED 3TB (ZFS 2x3 Striped RaidZ1)- Fractal Design Node 304

      The post was edited 1 time, last by cabrio_leo ().

    • klorinczi wrote:

      Should not have performance problems.
      The problem clearly comes from OMV 3.
      Clearly? What is the problem then? The error is a javascript error which means the client is involved as well. This means the browser, networking, and the server are all involved. Why doesn't everyone get the error? Why is the system performing a relatively high resource action in pretty much all of the situations I have seen this involved with? I get that multiple people are seeing this but it is not easy to diagnose especially when it can't be recreated on purpose.

      klorinczi wrote:

      Is debug mode implemented in OMV at all?
      Yep and it works very well.
      monit stop omv-engined
      omv-engined -df
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      klorinczi wrote:

      Should not have performance problems.
      The problem clearly comes from OMV 3.
      Clearly? What is the problem then? The error is a javascript error which means the client is involved as well. This means the browser, networking, and the server are all involved. Why doesn't everyone get the error? Why is the system performing a relatively high resource action in pretty much all of the situations I have seen this involved with? I get that multiple people are seeing this but it is not easy to diagnose especially when it can't be recreated on purpose.

      klorinczi wrote:

      Is debug mode implemented in OMV at all?
      Yep and it works very well.
      monit stop omv-engined
      omv-engined -df
      At least 2 of 5 HDDs in the server has bad sectors (content moved to reserved space). At least one doesn't pass short SMART test.
      This might be the reason of the error, and the reason why doesn't happen for everybody.


      Can I increase somewhere the javascript gui response timeout?

      I will try the debug mode later.

      Sent with Tapatalk from my SM-N9005
    • klorinczi wrote:

      Can I increase somewhere the javascript gui response timeout?
      Probably but I don't know where it is. I think that is avoiding the problem as well. Failing drives mean commands aren't returning in time and that is a timeout not set by OMV.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      klorinczi wrote:

      Can I increase somewhere the javascript gui response timeout?
      Probably but I don't know where it is. I think that is avoiding the problem as well. Failing drives mean commands aren't returning in time and that is a timeout not set by OMV.
      I think, that a failing drive should not cause failure of the GUI.

      Furthermore, the GUI should warn & display the drive failure.

      Sent with Tapatalk from my SM-N9005
    • klorinczi wrote:

      I think, that a failing drive should not cause failure of the GUI.

      Furthermore, the GUI should warn & display the drive failure.
      Great thought but OMV doesn't do magic. Any command run from the command line to query a drive's status will be very slow if it has failed in certain ways. OMV uses these same commands. A commercial NAS vendor can show warnings/failures like this because they always have the same hardware. OMV does not have that luxury. Sleeping drives can also appear to be failed if not given enough time to start.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      klorinczi wrote:

      I think, that a failing drive should not cause failure of the GUI.

      Furthermore, the GUI should warn & display the drive failure.
      Great thought but OMV doesn't do magic. Any command run from the command line to query a drive's status will be very slow if it has failed in certain ways. OMV uses these same commands. A commercial NAS vendor can show warnings/failures like this because they always have the same hardware. OMV does not have that luxury. Sleeping drives can also appear to be failed if not given enough time to start.
      I think it is development decision how to react, when timeout happens.
      OMV developer decided to give a fatal error, with a dialog window to be confirmed.

      I think there could be another way to handle such situation.

      Android gives a warning window, when an app is unresponsive, giving some options:
      - wait
      - report
      - close app

      OMV could handle similar way.
      If GUI doesn't get response from the server, should display a dialog window with multiple choices:
      - wait (adds +1 minute timeout before next warning dialog shows)
      - report (do so automatic debug information collection, and report to the developers). The report way should also make possible to preview the debug informations to be sent.
      - close dialog.

      I think this would be a better way to handle such timeout situation.



      Sent with Tapatalk from my SM-N9005
    • Further possibility:
      If I execute a task from GUI, it should:
      - pass command from GUI to server
      - server starts execution, and writes result buffer continuously to a session log file until it is finished successfully or finished with error.
      - GUI should read session log file, when requested by the user from GUI (by pressing "Command log" button on Storage/File systems page) or display the finished command output in an informational dialog on any current page.

      This is how it should work, IMHO.

      Sent from my GT-I9305 using Tapatalk.
    • klorinczi wrote:

      If I execute a task from GUI, it should:
      - pass command from GUI to server
      - server starts execution, and writes result buffer continuously to a session log file until it is finished successfully or finished with error.
      - GUI should read session log file, when requested by the user from GUI (by pressing "Command log" button on Storage/File systems page) or display the finished command output in an informational dialog on any current page.
      This is what it currently does. BUT if the Linux command (not written by OMV) does not return any output (which is common), the OMV web interface shows the communication error (not fatal in my opinion since it will recover).
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • I have the same problem: 36 disks in the system and the normal smart disk listing does take too long and the javascript throws an error after about 20 seconds. The RPC would have been finished after 32 seconds.
      (@ryecoaaron Thank you for the help getting debug info)

      I tried to fiend the rpc js timeout settings but without luck. Anyone who knows where i can find them ?

      Cheers
    • The only timeout I can find is the HTTP timeout request in /usr/share/php/openmediavault/globals.inc and it is set to 60 seconds.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!