cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9283) cloudstack-usage fails to start throwing Integer exception during PID retrieval
Date Wed, 10 Feb 2016 15:51:18 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141032#comment-15141032
] 

ASF GitHub Bot commented on CLOUDSTACK-9283:
--------------------------------------------

GitHub user davidamorimfaria opened a pull request:

    https://github.com/apache/cloudstack/pull/1409

    CLOUDSTACK-9283: add pid to java arguments in cloudstack-usage.service

    cloudstack-usage fails to start throwing Integer exception during PID retrieval, and the
service keeps restarting after 10s (as defined in the systemd service definition).
    
    Adding the pid to the java arguments in the systemd service definition makes it stop looping
in centos7


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/davidamorimfaria/cloudstack CLOUDSTACK-9283

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1409.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1409
    
----
commit ce180796e9c6f2a1a96d5ae51f8a1ab592c42090
Author: David Amorim Faria <d.amorim-faria@tech.leaseweb.com>
Date:   2016-02-10T15:46:03Z

    CLOUDSTACK-9283: add pid to java arguments in systemd/cloudstack-usage.service

----


> cloudstack-usage fails to start throwing Integer exception during PID retrieval
> -------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9283
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9283
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Usage
>    Affects Versions: 4.7.0
>         Environment: CentOS 7, systemd, packages from official repo
>            Reporter: Linas Žilinskas
>
> I have very little knowledge of java, but I looked at the code where the exception is
thrown. The code is 
> {code}_pid = Integer.parseInt(System.getProperty("pid"));{code} 
> Based on the information I found, I guess the command line requires -Dpid=$$ to be passed,
which isn't. I modified the systemd service to include the parameter and service now starts.
I'm not sure if this is something specific to my environment or not, but seems strange that
this could go unnoticed.
> {code}
> 12:49:27,981 DEBUG UsageManagerImpl:187 - Checking to see if usage.vmops.pid exists.
> 12:49:27,982  INFO UsageManagerImpl:195 - Implementation Version is 4.7.0
> 12:49:28,737 DEBUG UsageManagerImpl:218 - Usage stats aggregation time zone: GMT
> 12:49:28,738 DEBUG UsageManagerImpl:250 - Execution Time: Wed Feb 10 12:25:00 UTC 2016
> 12:49:28,738 DEBUG UsageManagerImpl:252 - Current Time: Wed Feb 10 12:49:28 UTC 2016
> java.lang.NumberFormatException: null
>         at java.lang.Integer.parseInt(Integer.java:542)
>         at java.lang.Integer.parseInt(Integer.java:615)
>         at com.cloud.usage.UsageManagerImpl.configure(UsageManagerImpl.java:267)
>         at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:116)
>         at com.cloud.usage.UsageServer.start(UsageServer.java:61)
>         at com.cloud.usage.UsageServer.main(UsageServer.java:47)
> 12:49:28,745 DEBUG DefaultListableBeanFactory:243 - Returning cached instance of singleton
bean 'usageManagerImpl'
> 12:49:28,745  INFO UsageServer:70 - UsageServer ready...
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message