[jira] Created: (CONTINUUM-2382) 'continuum-buildagent stop' Fails on Solaris 9

View: New views
3 Messages — Rating Filter:   Alert me  

[jira] Created: (CONTINUUM-2382) 'continuum-buildagent stop' Fails on Solaris 9

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

'continuum-buildagent stop' Fails on Solaris 9
----------------------------------------------

                 Key: CONTINUUM-2382
                 URL: http://jira.codehaus.org/browse/CONTINUUM-2382
             Project: Continuum
          Issue Type: Bug
          Components: Distributed Builds
    Affects Versions: 1.3.4
         Environment: Solaris 9
            Reporter: George Snyder


Arguments 'stop', 'restart', and 'status' erroneously remove the PID file if the installation path is too long.  They print a message such as:

  Removed stale pid file: /opt/continuum/apache-continuum-buildagent-1.3.4-B/bin/../logs/continuum-buildagent.pid

'stop' and 'restart' therefore do not stop the running process, which can result in multiple buildagent processes running.

The script tries to find the process ID by running 'ps' on the number in the PID file, and grepping that for the original startup command line.  For example:

  + /usr/bin/ps -p 17058 -o args
  + grep /opt/continuum/apache-continuum-buildagent-1.3.4-B/bin/./wrapper-solaris-sparc-32

Unfortunately 'grep' fails because, the 'ps' output is truncated, e.g.:
  /opt/continuum/apache-continuum-buildagent-1.3.4-B/bin/./wrapper-solaris-sparc-

Recommendation: Grep for a shorter pattern.

Workaround: Install the build agent in a shorter path, or create a short symbolic link to it.


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Commented: (CONTINUUM-2382) 'continuum-buildagent stop' Fails on Solaris 9

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message


    [ http://jira.codehaus.org/browse/CONTINUUM-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193898#action_193898 ]

George Snyder commented on CONTINUUM-2382:
------------------------------------------

Correction: Creating a symbolic link to the installation directory doesn't help, because the script expands it to the full physical path.

> 'continuum-buildagent stop' Fails on Solaris 9
> ----------------------------------------------
>
>                 Key: CONTINUUM-2382
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2382
>             Project: Continuum
>          Issue Type: Bug
>          Components: Distributed Builds
>    Affects Versions: 1.3.4
>         Environment: Solaris 9
>            Reporter: George Snyder
>
> Arguments 'stop', 'restart', and 'status' erroneously remove the PID file if the installation path is too long.  They print a message such as:
>   Removed stale pid file: /opt/continuum/apache-continuum-buildagent-1.3.4-B/bin/../logs/continuum-buildagent.pid
> 'stop' and 'restart' therefore do not stop the running process, which can result in multiple buildagent processes running.
> The script tries to find the process ID by running 'ps' on the number in the PID file, and grepping that for the original startup command line.  For example:
>   + /usr/bin/ps -p 17058 -o args
>   + grep /opt/continuum/apache-continuum-buildagent-1.3.4-B/bin/./wrapper-solaris-sparc-32
> Unfortunately 'grep' fails because, the 'ps' output is truncated, e.g.:
>   /opt/continuum/apache-continuum-buildagent-1.3.4-B/bin/./wrapper-solaris-sparc-
> Recommendation: Grep for a shorter pattern.
> Workaround: Install the build agent in a shorter path, or create a short symbolic link to it.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Updated: (CONTINUUM-2382) 'continuum-buildagent stop' Fails on Solaris 9

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message


     [ http://jira.codehaus.org/browse/CONTINUUM-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wendy Smoak updated CONTINUUM-2382:
-----------------------------------

    Fix Version/s: Backlog

> 'continuum-buildagent stop' Fails on Solaris 9
> ----------------------------------------------
>
>                 Key: CONTINUUM-2382
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2382
>             Project: Continuum
>          Issue Type: Bug
>          Components: Distributed Builds
>    Affects Versions: 1.3.4
>         Environment: Solaris 9
>            Reporter: George Snyder
>             Fix For: Backlog
>
>
> Arguments 'stop', 'restart', and 'status' erroneously remove the PID file if the installation path is too long.  They print a message such as:
>   Removed stale pid file: /opt/continuum/apache-continuum-buildagent-1.3.4-B/bin/../logs/continuum-buildagent.pid
> 'stop' and 'restart' therefore do not stop the running process, which can result in multiple buildagent processes running.
> The script tries to find the process ID by running 'ps' on the number in the PID file, and grepping that for the original startup command line.  For example:
>   + /usr/bin/ps -p 17058 -o args
>   + grep /opt/continuum/apache-continuum-buildagent-1.3.4-B/bin/./wrapper-solaris-sparc-32
> Unfortunately 'grep' fails because, the 'ps' output is truncated, e.g.:
>   /opt/continuum/apache-continuum-buildagent-1.3.4-B/bin/./wrapper-solaris-sparc-
> Recommendation: Grep for a shorter pattern.
> Workaround: Install the build agent in a shorter path, or create a short symbolic link to it.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira