Skip to content

Service Status Fix#310

Merged
akutz merged 1 commit intorexray:masterfrom
akutz:bugfix/service-status
Feb 20, 2016
Merged

Service Status Fix#310
akutz merged 1 commit intorexray:masterfrom
akutz:bugfix/service-status

Conversation

@akutz
Copy link
Copy Markdown
Member

@akutz akutz commented Feb 19, 2016

This patch fixes issue #293 where a stale PID file would incorrectly indicate that REX-Ray was running if the status command was issued.

@akutz akutz added the bugfix label Feb 19, 2016
@akutz akutz self-assigned this Feb 19, 2016
@akutz akutz added this to the 0.3.2 milestone Feb 19, 2016
This patch fixes issue rexray#262 where a stale PID file would incorrectly
indicate that REX-Ray was running if the `status` command was issued.
@akutz akutz force-pushed the bugfix/service-status branch from a436433 to f20bf54 Compare February 19, 2016 23:55
@akutz
Copy link
Copy Markdown
Member Author

akutz commented Feb 20, 2016

Hi @clintonskitson,

I just verified this on a Linux system. Merging.

[0]akutz@poppy:Linux-x86_64$ sudo ./rexray service status
DEBU[0000] updated log level                             logLevel=debug
REX-Ray is stopped
[0]akutz@poppy:Linux-x86_64$ sudo ./rexray service stop
DEBU[0000] updated log level                             logLevel=debug
REX-Ray is already stopped
DEBU[0000] exiting with error code 1                    
[1]akutz@poppy:Linux-x86_64$ sudo ./rexray service start
DEBU[0000] updated log level                             logLevel=debug
INFO[0000] [linux]                                      
INFO[0000] [docker]                                     
INFO[0000] [isilon]                                     
DEBU[0000] core get drivers                              osDrivers=[linux] storageDrivers=[isilon] volumeDrivers=[docker]
INFO[0000] docker volume driver initialized              availabilityZone= iops= moduleName= provider=docker size= volumeRootPath=/data volumeType=
INFO[0000] storage driver initialized                    dataSubnet=172.17.177.0/24 endpoint=https://172.17.177.230:8080 group= insecure=true moduleName= password=****** provider=Isilon userName=root volumePath=/rexray
INFO[0000] os driver initialized                         moduleName= provider=linux
DEBU[0000] invoking service start                        os.Args=[./rexray service start]
Starting REX-Ray...DEBU[0000] trying to start service                       client=/tmp/pBYNLzigKwgREXsBsxyllGnfiUoQhiBv.sock
time="2016-02-19T18:06:01-06:00" level=debug msg="updated log level" logLevel=debug 
time="2016-02-19T18:06:01-06:00" level=debug msg="invoking service start" os.Args=[/media/psf/go/src/github.com/emccode/rexray/.build/bin/Linux-x86_64/rexray start --client=/tmp/pBYNLzigKwgREXsBsxyllGnfiUoQhiBv.sock --logLevel=debug --host=tcp://:7979] 
DEBU[0000] accepted connection                          
DEBU[0000] received data                                
SUCCESS!

  The REX-Ray daemon is now running at PID 2409. To
  shutdown the daemon execute the following command:

    sudo /media/psf/go/src/github.com/emccode/rexray/.build/bin/Linux-x86_64/rexray stop

[0]akutz@poppy:Linux-x86_64$ sudo ./rexray service status
DEBU[0000] updated log level                             logLevel=debug
REX-Ray is running at PID 2409
[0]akutz@poppy:Linux-x86_64$ sudo kill -9 2409
[0]akutz@poppy:Linux-x86_64$ sudo ./rexray service status^C
[130]akutz@poppy:Linux-x86_64$ cat /var/run/rexray/rexray.pid 
2409[0]akutz@poppy:Linux-x86_sudo ./rexray service status
DEBU[0000] updated log level                             logLevel=debug
REX-Ray is stopped
[0]akutz@poppy:Linux-x86_64$ ls /var/run/rexray/
total 0
drwxr-xr-x.  2 root  40 Feb 19 18:06 ./
drwxr-xr-x. 27 root 800 Feb 19 18:05 ../
[0]akutz@poppy:Linux-x86_64$ 

akutz added a commit that referenced this pull request Feb 20, 2016
@akutz akutz merged commit de861cb into rexray:master Feb 20, 2016
@akutz akutz deleted the bugfix/service-status branch February 20, 2016 00:08
akutz added a commit to akutz/rexray that referenced this pull request Feb 23, 2016
ENHANCEMENTS
* ScaleIO volume name limitation rexray#304
* Docker cache volumes for path operations rexray#306
* Config file validation rexray#312
* Better logging rexray#296

BUG FIXES
* ScaleIO re-authentication issue rexray#303
* Docker XtremIO create volume issue rexray#307
* Service status is reported correctly rexray#310

UPDATES
* Go 1.6 rexray#308
akutz added a commit to akutz/rexray that referenced this pull request Mar 4, 2016
This patch marks the release of REX-Ray 0.3.2!

NEW FEATURES
* Support for Docker 1.10 and Volume Plugin Interface 1.2 rexray#273
* Stale PID File Prevents Service Start rexray#258
* Module/Personality Support rexray#275
* Isilon Preemption rexray#231
* Isilon Snapshots rexray#260
* boot2Docker Support rexray#263
* ScaleIO Dynamic Storage Pool Support rexray#267

ENHANCEMENTS
* Improved installation documentation rexray#331
* ScaleIO volume name limitation rexray#304
* Docker cache volumes for path operations rexray#306
* Config file validation rexray#312
* Better logging rexray#296
* Documentation Updates rexray#285

BUG FIXES
* Fixes issue with daemon process getting cleaned as part of
  SystemD Cgroup rexray#327
* Fixes regression in 0.3.2 RC3/RC4 resulting in no log file rexray#319
* Fixes no volumes returned on empty list rexray#322
* Fixes "Unsupported FS" when mounting/unmounting with EC2 rexray#321
* ScaleIO re-authentication issue rexray#303
* Docker XtremIO create volume issue rexray#307
* Service status is reported correctly rexray#310

UPDATES
* <del>Go 1.6 rexray#308</del>

THANK YOU
* Dan Forrest
* Kapil Jain
* Alex Kamalov
This was referenced Mar 4, 2016
akutz added a commit to akutz/rexray that referenced this pull request Jul 24, 2017
Update EBS Test Vagrantfile w codedellemc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant