HP Envy 4500 Support about node-hp-scan-to HOT 14 CLOSED

@cullenmcdermott I'll try to read that information and act accordingly

from node-hp-scan-to.

@cullenmcdermott Could you send the full log because what's before could be very useful to understand why the app is stuck in this state ?

Thanks

from node-hp-scan-to.

Hey, sorry for the delay on this. I'll grab the full log later this afternoon or this evening and share it here.

from node-hp-scan-to.

Here's a gist of the logs from when I start the container, then I perform a successful scan, then try to start a second one and it just keeps looping with that last log.

https://gist.github.com/cullenmcdermott/9bc441298002660bb9182c4e1f7d559d

from node-hp-scan-to.

Hi @cullenmcdermott thanks for the full logs provided

Could you send me the xml content of http://1192.168.0.212/WalkupScanToComp/WalkupScanToCompCaps

Mine is have this content

<?xml version="1.0" encoding="UTF-8"?>
<!---->
<wus:WalkupScanToCompCaps xsi:schemaLocation="http://www.hp.com/schemas/imaging/con/ledm/walkupscan/2010/09/28 ../../schemas/WalkupScanToComp.xsd" xmlns:dd="http://www.hp.com/schemas/imaging/con/dictionaries/1.0/" xmlns:wus="http://www.hp.com/schemas/imaging/con/ledm/walkupscan/2010/09/28" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<dd:Version>
		<dd:Revision>SVN-IPG-LEDM.351</dd:Revision>
	</dd:Version>
	<wus:MaxNetworkDestinations>15</wus:MaxNetworkDestinations>
	<wus:SupportsMultiItemScanFromPlaten>true</wus:SupportsMultiItemScanFromPlaten>
	<wus:UserActionTimeout>
		<dd:ValueFloat>60</dd:ValueFloat>
		<dd:Unit>seconds</dd:Unit>
	</wus:UserActionTimeout>
	<wus:ShortcutSupport access="readOnly">
		<wus:Shortcut>SavePDF</wus:Shortcut>
		<wus:Shortcut>SaveJPEG</wus:Shortcut>
		<wus:Shortcut>EmailPDF</wus:Shortcut>
		<wus:Shortcut>EmailJPEG</wus:Shortcut>
		<wus:Shortcut>GeneralScan</wus:Shortcut>
	</wus:ShortcutSupport>
</wus:WalkupScanToCompCaps>

I guess you don't have SupportsMultiItemScanFromPlaten set to true

from node-hp-scan-to.

Yeah it looks like that is set to false. I'm looking to see if there's a way to enable that.

<!---->
<wus:WalkupScanToCompCaps xsi:schemaLocation="http://www.hp.com/schemas/imaging/con/ledm/walkupscan/2010/09/28 WalkupScanToComp.xsd">
<dd:Version>
<dd:Revision>SVN-IPG-LEDM.351</dd:Revision>
</dd:Version>
<wus:MaxNetworkDestinations>15</wus:MaxNetworkDestinations>
<wus:SupportsMultiItemScanFromPlaten>false</wus:SupportsMultiItemScanFromPlaten>
<wus:UserActionTimeout>
<dd:ValueFloat>60</dd:ValueFloat>
<dd:Unit>seconds</dd:Unit>
</wus:UserActionTimeout>
</wus:WalkupScanToCompCaps>

from node-hp-scan-to.

@cullenmcdermott can you try with this https://hub.docker.com/layers/237042732/manuc66/node-hp-scan-to/feature_SupportsMultiItemScanFromPlaten-false/images/sha256-96fd84e694c1523f6e944436a5aa61a8b4f9e506efaa49253314984bfe8f8d14?context=repo and send the full logs in case of errors ?

Thanks

from node-hp-scan-to.

That doesn't appear to run correctly. It seems to start, but never emits any logs, and my scanner is unable to reach it.

from node-hp-scan-to.

Could you confirm you did not forget the parameter that gives the ip address ?

from node-hp-scan-to.

Yes I'm using the exact same config just changing the tag. Here's the config I'm using just for clarity, its a portion of a Nomad Jobspec. Changing the image line to use the tag feature_SupportsMultiItemScanFromPlaten-false does not work for me.

    task "hp-scan" {

      env {
        IP = "192.168.0.212"
        CMDLINE = "-D"
        PATTERN="\"scan\"_dd.mm.yyyy_hh:MM:ss"
        TZ = "America/Boise"
      }

      resources {
        cpu = 250
        memory = 250
      }

      driver = "docker"

      config {
        image = "manuc66/node-hp-scan-to"
        hostname = "document-ingest"
        mount {
          target = "/scan"
          source = "paperless-consume"
          volume_options {
            driver_config {
              name = "local"
              options = {
                type = "nfs"
                device = ":/volume1/paperless-consume"
                o = "addr=192.168.0.234,vers=3,timeo=180,tcp,rw"
              }
            }
          }
        }
      }
    }

from node-hp-scan-to.

I have the same issue when using the docker container too, (but not when launching from npm)

I don't know why

from node-hp-scan-to.

The starting issue is not linked to changes, see #497

from node-hp-scan-to.

@cullenmcdermott if you still even want to test the feature, you can docker exec -it docker_name sh while the container is in freezed state and then launch the app manually with node index.js command (see here to translate the arguments)

from node-hp-scan-to.

@cullenmcdermott issue #497 has been fixed, can you try "manuc66/node-hp-scan-to:latest" ? (The PR has been merged)

from node-hp-scan-to.