Re: [HTCondor-users] SOAP not available in this daemon

[Ben Cotton <ben.cotton@xxxxxxxxxxxxxxxxxx>]

The SOAP interface isn't available on the Shadow or Startd (just the
Scheduler and Collector, I believe), so these messages are expected.
What are you trying to do with SOAP calls to those daemons?

On Thu, Jun 1, 2017 at 9:47 AM, Guang.Wei <492096437@xxxxxx> wrote:
> Shadowlog:
> 06/01/17 21:27:09 ******************************************************
> 06/01/17 21:27:09 ** condor_shadow (CONDOR_SHADOW) STARTING UP
> 06/01/17 21:27:09 ** /usr/sbin/condor_shadow
> 06/01/17 21:27:09 ** SubsystemInfo: name=SHADOW type=SHADOW(6)
> class=DAEMON(1)
> 06/01/17 21:27:09 ** Configuration: subsystem:SHADOW local:<NONE>
> class:DAEMON
> 06/01/17 21:27:09 ** $CondorVersion: 8.4.1 Oct 26 2015 BuildID: 346648 $
> 06/01/17 21:27:09 ** $CondorPlatform: X86_64-RedHat_6.7 $
> 06/01/17 21:27:09 ** PID = 3928122
> 06/01/17 21:27:09 ** Log last touched 6/1 21:12:06
> 06/01/17 21:27:09 ******************************************************
> 06/01/17 21:27:09 Using config source: /etc/condor/condor_config
> 06/01/17 21:27:09 Using local config sources:
> 06/01/17 21:27:09    /etc/condor/condor_config.local
> 06/01/17 21:27:09 config Macros = 106, Sorted = 106, StringBytes = 3267,
> TablesBytes = 1744
> 06/01/17 21:27:09 CLASSAD_CACHING is OFF
> 06/01/17 21:27:09 Daemon Log is logging: D_ALWAYS D_ERROR
> 06/01/17 21:27:09 Daemoncore: Listening at <0.0.0.0:9846> on TCP (ReliSock).
> 06/01/17 21:27:09 DaemonCore: command socket at
> <xxxx:9846?addrs=xxxx-9846&noUDP>
> 06/01/17 21:27:09 DaemonCore: private command socket at
> <xxx:9846?addrs=xxx-9846>
> 06/01/17 21:27:09 Initializing a PARALLEL shadow for job 51864.0
> 06/01/17 21:27:09 (51864.0) (3928122): Setting parallel shutdown policy to
> WAIT_FOR_ALL
> 06/01/17 21:27:10 (51864.0) (3928122): Request to run on slot3@xxxxxxxxxxxxx
> <xxxxxx:9761?addrs=xxxx-9761> was ACCEPTED
> 06/01/17 21:27:10 (51864.0) (3928122): Request to run on
> <x.x.xx:9730?addrs=x.x.xx-9730> <xxxxx:9730?addrs=xxxx-9730> was ACCEPTED
> 06/01/17 21:27:10 (51864.0) (3928122): File transfer completed successfully.
> 06/01/17 21:27:20 (51864.0) (3928122): Received HTTP GET connection from
> <10.254.4.50:33092>
> 06/01/17 21:27:20 (51864.0) (3928122): SOAP not available in this daemon,
> ignoring SOAP connection attempt...
> 06/01/17 21:27:20 (51864.0) (3928122): About to serve HTTP request...
> 06/01/17 21:27:20 (51864.0) (3928122): SOAP not available in this daemon,
> ignoring SOAP request...
> 06/01/17 21:27:20 (51864.0) (3928122): Completed servicing HTTP request
> 06/01/17 21:27:20 (51864.0) (3928122): File transfer completed successfully.
> 06/01/17 21:31:10 (51864.0) (3928122): File transfer completed successfully.
> 06/01/17 21:31:10 (51864.0) (3928122): File transfer completed successfully.
> 06/01/17 21:31:11 (51864.0) (3928122): Job 51864.0 terminated: exited with
> status 0
> 06/01/17 21:31:11 (51864.0) (3928122): Reporting job exit reason 100 and
> attempting to fetch new job.
> 06/01/17 21:31:11 (51864.0) (3928122): **** condor_shadow (condor_SHADOW)
> pid 3928122 EXITING WITH STATUS 100
>
>
>
> ------------------ Original ------------------
> From:  "492096437@xxxxxx";<492096437@xxxxxx>;
> Date:  Wed, May 31, 2017 05:47 PM
> To:  "htcondor-users"<htcondor-users@xxxxxxxxxxx>;
> Subject:  [HTCondor-users] SOAP not available in this daemon
>
> configure:
> WEB_ROOT_DIR=$(RELEASE_DIR)/web
> ENABLE_SOAP=TRUE
> ENABLE_WEB_SERVER=TRUE
> ALLOW_SOAP=*
> HOSTALLOW_READ = *
> HOSTALLOW_WRITE = *
> QUEUE_ALL_USERS_TRUSTED=TRUE
> SCHEDD_ARGS=-p 8089
> SOAP_LEAVE_IN_QUEUE = ((JobStatus==4) && ((ServerTime - CompletionDate) <
> (60 * 60 * 24)))
>
> StartLog:
> 05/31/17 17:39:31 SOAP not available in this daemon, ignoring SOAP
> connection attempt...
> 05/31/17 17:39:31 About to serve HTTP request...
> 05/31/17 17:39:31 SOAP not available in this daemon, ignoring SOAP
> request...
> 05/31/17 17:39:31 Completed servicing HTTP request
>
> How to solve "SOAP not available in this daemon"?
>
> Thanks,
> Allen
>
>
>
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/



-- 
Ben Cotton
Technical Marketing Manager

Cycle Computing
Better Answers. Faster.

http://www.cyclecomputing.com
twitter: @cyclecomputing