I’m working in Visual C# Express (no WindowsService template) and attempted to write my first service. I’ve gotten through a few issues already, but I’m a bit stumped on this one. I’m receiving the following error trying to run the InstallUtil in the Release folder of my project:
An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: The specified service already exists
I think it is probably worth noting here that I have run the install many times previous to this, though none of these attempts have been successful, for wholly separate reasons.
I have also searched and found other replies to similar issues, but in most cases it seems this is caused by leftover «stuff» in the registry. I tried searching my registry for «MediaManager» (the service is called MediaManagerFileBackupService and the exe file is MediaManager.Manager.Service.exe) and came up with nothing.
My installer code is very simple; I have a class derived from ServiceInstaller with the RunInstallerAttribute set to true, with the following code in the constructor:
string strSource = «MediaManagerFileBackupService»;
ServiceName = strSource;
ServiceProcessInstaller spiFileBackup = new ServiceProcessInstaller();
spiFileBackup.Account = ServiceAccount.LocalSystem;
spiFileBackup.Username = null;
spiFileBackup.Password = null;
spiFileBackup.Parent = this;
ServiceInstaller siFileBackup = new ServiceInstaller();
siFileBackup.DisplayName = strSource;
siFileBackup.ServiceName = strSource;
siFileBackup.StartType = ServiceStartMode.Manual;
siFileBackup.Parent = this;
Installers.Add(spiFileBackup);
Installers.Add(siFileBackup);
Below I’ve copied the logs for the install. I may be misunderstanding the log output, but it looks to me like the InstallUtil is trying install the service at least two separate times, if not more. I’ve bolded and italicized the section that looks like it’s trying to install more than once (in the console log, it is directly after the bold/ italicized section that I get the «The specified service already exists» error).
InstallUtil.InstallLog
Running a transacted installation.
Beginning the Install phase of the installation.
See the contents of the log file for the C:UsersEvanDocumentsVisual Studio 2008ProjectsMediaManagerMediaManager.Manager.ServicebinReleaseMediaManager.Manager.Service.exe assembly’s progress.
The file is located at C:UsersEvanDocumentsVisual Studio 2008ProjectsMediaManagerMediaManager.Manager.ServicebinReleaseMediaManager.Manager.Service.InstallLog.An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: The specified service already existsThe Rollback phase of the installation is beginning.
See the contents of the log file for the C:UsersEvanDocumentsVisual Studio 2008ProjectsMediaManagerMediaManager.Manager.ServicebinReleaseMediaManager.Manager.Service.exe assembly’s progress.
The file is located at C:UsersEvanDocumentsVisual Studio 2008ProjectsMediaManagerMediaManager.Manager.ServicebinReleaseMediaManager.Manager.Service.InstallLog.The Rollback phase completed successfully.
The transacted install has completed.
MediaManager.Manager.Service.InstallLog
Installing assembly ‘C:UsersEvanDocumentsVisual Studio 2008ProjectsMediaManagerMediaManager.Manager.ServicebinReleaseMediaManager.Manager.Service.exe’.
Affected parameters are:
logtoconsole =
assemblypath = C:UsersEvanDocumentsVisual Studio 2008ProjectsMediaManagerMediaManager.Manager.ServicebinReleaseMediaManager.Manager.Service.exe
logfile = C:UsersEvanDocumentsVisual Studio 2008ProjectsMediaManagerMediaManager.Manager.ServicebinReleaseMediaManager.Manager.Service.InstallLog
Installing service MediaManagerFileBackupService…
Creating EventLog source MediaManagerFileBackupService in log Application…
Installing service MediaManagerFileBackupService…
Service MediaManagerFileBackupService has been successfully installed.
Creating EventLog source MediaManagerFileBackupService in log Application…
Installing service MediaManagerFileBackupService…
Creating EventLog source MediaManagerFileBackupService in log Application…
Rolling back assembly ‘C:UsersEvanDocumentsVisual Studio 2008ProjectsMediaManagerMediaManager.Manager.ServicebinReleaseMediaManager.Manager.Service.exe’.
Affected parameters are:
logtoconsole =
assemblypath = C:UsersEvanDocumentsVisual Studio 2008ProjectsMediaManagerMediaManager.Manager.ServicebinReleaseMediaManager.Manager.Service.exe
logfile = C:UsersEvanDocumentsVisual Studio 2008ProjectsMediaManagerMediaManager.Manager.ServicebinReleaseMediaManager.Manager.Service.InstallLog
Restoring event log to previous state for source MediaManagerFileBackupService.
Restoring event log to previous state for source MediaManagerFileBackupService.
Service MediaManagerFileBackupService is being removed from the system…
Service MediaManagerFileBackupService was successfully removed from the system.
Restoring event log to previous state for source MediaManagerFileBackupService.
Any help on this issue would be greatly appreciated. Thanks in advance.
-
#1
Good Day!
Does anybody tested TS on the Latest Windows 10 LTSC 1809 ?
Seems all working fine but i get this annoying Error Message (see attch photo.)
This error related to Disable and lock Turbo Power Limits option. This happening everytime when TS starts. If i turn off this option i dont get this error.
On the Windows Home Edition i didn’t have this problem. Dont like to roll back to Home Edition with lots of preinstalled garbage 
I didnt find any solution in internet : (
Any suggestions how to resolve this problem ?
-
#3
Are you using Windows Defender?
If Windows 10 -1809 or Windows Defender does not like the RwDrv.sys file / driver, you will not be able to use the Disable and Lock Turbo Power Limits feature. I did not write that driver so I have no way to fix the part of ThrottleStop that depends on that driver.
-
#4
Are you using Windows Defender?
If Windows 10 -1809 or Windows Defender does not like the RwDrv.sys file / driver, you will not be able to use the Disable and Lock Turbo Power Limits feature. I did not write that driver so I have no way to fix the part of ThrottleStop that depends on that driver.
Not OP but I’m getting the same error from ThrottleStop and I am using Avast. I am also on Windows 10 — 1809.
Based on what you’re saying since we are getting the error then it is not working, right? So does that mean I should just leave it unchecked for now?
-
#5
What is your Windows 10 version; Home, Pro, LTSC, ???
I am using Windows 10 Pro — 1809 with all of the latest updates and I am not having any problems using the Disable and Lock feature. After thousands of downloads, there have been very few complaints about this so I am assuming that not a lot of people have this problem.
I created this folder:
C:Program Files (x86)ThrottleStop
All of the ThrottleStop related files are in that folder including ThrottleStop.exe and the RwDrv.sys file that I downloaded from Mega.
https://mega.nz/#!CNNA0SoC!Z2Xi2icwX4d4jzW016dKnKGhVglWmSSPpgiRU7VCG6g
You have to unzip the file after you download it. Copy RwDrv.sys into the ThrottleStop folder.
@Falcorion — If you still cannot get this feature working for you then you will not be able to use it.
-
#6
What is your Windows 10 version; Home, Pro, LTSC, ???
@Falcorion — If you still cannot get this feature working for you then you will not be able to use it.
My Windows 10 version is Home. We previously went back and forth a bit during my initial set up and I have mine configured identically to you. This feature used to work then suddenly I was getting the error when ThrottleStop would start, I’m assuming it’s update related. With the box unchecked I no longer get the error.
-
#7
If you are not using ThrottleStop 8.70.6, download the latest version from TechPowerUp.
https://www.techpowerup.com/download/techpowerup-throttlestop/
Are you using any other software that also uses the RwDrv driver? There might be a problem if you have RWEverything open. Are you in an account with Admin privileges or are you in a Limited account. Just trying to think what might be different on your computer.
Check that you and Windows have full access to this file.
Last edited: Apr 6, 2019
-
#8
That’s the version I am on. Double checked permissions and tried again, no change.
How could I find out if something else is using that driver? I am not using RWEverything.
-
#9
@unclewebb I am also experiencing this issue. Same thing everything just worked in the past. Upon updating Win 10 to 1809, This error starts to pop whenever attempt to launch ThrottleStop. But I notice one thing thou. I tested version 8.60 and the issue goes away. So there must be something from the current 8.70.6 which 8.60 does not have which is what that is causing the issue. At from a logic side of thing given the situation is probably the case?
-
#10
@Kopicha — The change between 8.60 and 8.70.6 is the FIVR — Disable and Lock Turbo Power Limits feature which uses the RwDrv.sys driver file. Are you trying to use that feature? Did you download and install RwDrv.sys in your ThrottleStop folder?
If you need that feature, try disabling the Windows Memory integrity check.
http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-1005#post-10896646
I am running ThrottleStop 8.70.6 on Windows 10 — 1809 without any problems. My laptop has an older 4th Gen processor which does not support the Core isolation — memory integrity feature.
-
#11
@Kopicha — The change between 8.60 and 8.70.6 is the FIVR — Disable and Lock Turbo Power Limits feature which uses the RwDrv.sys driver file. Are you trying to use that feature? Did you download and install RwDrv.sys in your ThrottleStop folder?
If you need that feature, try disabling the Windows Memory integrity check.
http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-1005#post-10896646
I am running ThrottleStop 8.70.6 on Windows 10 — 1809 without any problems. My laptop has an older 4th Gen processor which does not support the Core isolation — memory integrity feature.
Thank you that solve the problem simply disable the Memory Integrity feature
-
#12
Hey guys, Necro from beyond — I was just struggling with this problem and actually managed to fix it.
Unfortunately, I was on the brink of just doing a clean install of Windows because this was literally working earlier today, no updates or anything, and then it died… So I wasn’t exactly taking notes.
The long and short of what fixed it was that I went into regedit, did a «Find…» for rwdrv and it found one key. The key started with s… something, looked like a name, followed by _rwdrv at the end.
In the values for said key, it specifically referenced C:Throttlestop (which is where my installation is located), so I felt pretty confident when I pressed delete.
Didn’t even need to reboot, just disabled FIVR and re-enabled FIVR and it started working instantly.
The key hasn’t reappeared yet — I’m going to reboot, etc. and if it comes back I will edit my reply here with the exact name of the key.
Edit: Well, the key hasn’t reappeared.. But neither has my issue. Welp. Wish I was paying more attention at the time, but like I said — I was about to reinstall Windows because I was so frustrated with it
Last edited: Nov 29, 2019
-
#13
Hey, I’ve been struggling with this problem also, thanks for the tips.
I took @Hyatice’s advice and deleted the registry key that he mentioned — it wasn’t too difficult to find. The key is [HKEY_LOCAL_MACHINESYSTEMControlSet001ServicesSetecAstronomy_RwDrv].
I deleted the entire key, then turned off «Disable and Lock Turbo Power Limits» and turned it back on again, then rebooted the computer. No more error when ThrottleStop starts, and my computer is behaving itself again.
-
#14
Hi everyone, i did all the things suggested here but i still encounter a couple of errors, at startup i get the message Error starting the service:Access denied, and if i turn off «Disable and Lock Turbo Power Limits» and turn it back on i get Error starting the service: Insufficient System Resources Exist to Complete the Requested Service, i am running the latest version of throttlestop .
-
#15
@VladMr — Did you download and install the RwDrv.sys file into your ThrottleStop folder? Are you running any other software on your computer that uses the RwDrv.sys file? Do you have Admin privileges? Where is your ThrottleStop folder located? Did you move this folder after you first ran ThrottleStop?
Most people are not having problems. Tell me exactly what you did and maybe I can figure out what you did differently.
-
#16
@unclewebb
I installed a fresh copy of the throttlestop and installed RwDrv.sys file in the ThrottleStop folder , i am not sure how to check what other software uses RwDrv.sys and if you can show me how to check i will provide the details, I have admin privileges and i gave the ThrottleStop folder full permissions on every user , i installed the Throttlestop in C:/ProgramFiles(x86)/Throttlestop, it was allways intalled in this path. Also based on what i read on other forums, it might be a windows defender problem so i added the folder as an exclusion in Windows Defender settings. At startup only throttlestop and afterburner are set up to start .
@unclewebb , I am using a Dell inspiron 7577 with an i5 7300HQ, windows 10 pro 1909
this error has appeared some time ago but i was not paying attention to it untill i noticed that my CPU temperatures were higher than usual
Btw, i had the same error with Error creating service: The specified service already exists, after i deleted the registry key that was suggested here, it changed to Access Denied
Last edited: Dec 27, 2019
-
#17
How are you auto starting ThrottleStop when Windows boots up? That might be what is causing the problem.
I recommend using the Task Scheduler. Follow the guide I wrote exactly.
TechnologyGuide
Thank you for visiting the TechnologyGuide network. Unfortunately, these forums are no longer active. We extend a heartfelt thank you to the entire community for their steadfast support—it is really you, our readers, that drove
forum.notebookreview.com
i deleted the registry key
I have never had to modify the registry to get ThrottleStop to start up. I am not sure if that was good advice or not.
-
#18
@unclewebb i deleted this registry key [HKEY_LOCAL_MACHINESYSTEMControlSet001ServicesSetecAstronomy_RwDrv].
it helpet @Billious with his startup issues so i thought it might help .
i used this exact guide to set up throttle stop to start with the windows.
i will do it again just to be sure but i think this is not the issue, throttle stop starts at logon but it gives my this error ‘Error starting the service: Insufficient System Resources Exist to Complete the Requested Service ‘
@unclewebb i noticed that if i disable the Disable and Lock Turbo Power limits option the error does not appear
-
#19
The Disable and Lock feature is the only feature that uses the RwDrv.sys driver.
If you need that feature, did you try disabling the Windows Memory Integrity check as mentioned in post #10 in this thread?
-
#20
yes , memory integrity is off
-
#21
@VladMr — I am out of ideas. I know there are lots of other users running Windows 10 — 1909 and they are not having the problem you are having. I am not sure if there was a recent Windows Update or perhaps Windows Defender is preventing this from working correctly. I do not have access to any computers running Windows 10 — 1909 for testing purposes.
You will not be able to use the Disable and Lock Turbo Power Limits feature. I did not write the code for this feature. I will not be able to troubleshoot or fix the problem you are having. I am guessing that it is Windows Defender or whatever antivirus program you are using that is blocking this driver from being installed.
-
#22
@unclewebb — Hey , i tried yesterday to turn the memory integrity back on but windows is preventing to do so. i plan to install a fresh copy of windows so this issue would resolve, thank you for your time ! Merry Cristmas and Happy new year.
-
#23
Good Day!
Does anybody tested TS on the Latest Windows 10 LTSC 1809 ?
Seems all working fine but i get this annoying Error Message (see attch photo.)
This error related to Disable and lock Turbo Power Limits option. This happening everytime when TS starts. If i turn off this option i dont get this error.
On the Windows Home Edition i didn’t have this problem. Dont like to roll back to Home Edition with lots of preinstalled garbage
I didnt find any solution in internet : (
Any suggestions how to resolve this problem ?View attachment 118691
I figured out a way to solve it. I deleted the service from Registry and it worked if anyone’s still interested. ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices and then search for RWdrv if i remeber correctly and delete it
-
#24
Hi, I am running TS 8.70.6 in Windows 10 Home 1909. I wasn’t having any issues until installed Dolby Atmos, know I get a «Error creating service: (null)» message when TS runs, although it is not impeding it to run. Does the troubleshoot above solve this same issue?
Cheers!
-
#25
Dolby Atmos must be using the same RwDrv driver. The only feature in ThrottleStop that uses this driver is the FIVR Disable and Lock Turbo Power Limits feature. If you need Dolby Atmos more than Disable & Lock, disable that ThrottleStop feature and that error message should go away.
Hey guys,
I have a lot of containers that use the unless-stopped policy and after a daemon restart for testing that all works fine, somehow for the es container I got the error from the title… There is just one container that is named es…
I wanted to start it manually, but got the same error… this should have worked as it’s the same container that the message complaints about.
Here is some more info:
$ sudo docker info
Containers: 20
Running: 12
Paused: 0
Stopped: 8
Images: 1069
Server Version: 1.10.1
Storage Driver: overlay
Backing Filesystem: extfs
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
Volume: local
Network: null host overlay bridge
Kernel Version: 4.3.0-040300-generic
Operating System: Ubuntu 14.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.16 GiB
Name: seb
ID: 3IIK:AWIX:PLOR:BPQ4:XNEL:SSXQ:2GUL:VEKX:OVCQ:SCCX:MN2U:DTWH
WARNING: No swap limit support
Cluster store: consul://localhost:8500
Cluster advertise: 192.168.123.18:2375
$ sudo docker version
Client:
Version: 1.10.1
API version: 1.22
Go version: go1.5.3
Git commit: 9e83765
Built: Thu Feb 11 19:27:08 2016
OS/Arch: linux/amd64
Server:
Version: 1.10.1
API version: 1.22
Go version: go1.5.3
Git commit: 9e83765
Built: Thu Feb 11 19:27:08 2016
OS/Arch: linux/amd64
$ sudo docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7e63bf3754b0 hgdata1/focus:297f50a8ec59 "/bin/sh -c ./trap.sh" 18 minutes ago Up 16 minutes 8020/tcp focus-v7
35828cac56ea f06503660e96 "bash" 21 minutes ago Exited (130) 9 minutes ago small_curie
5bf6295f7c69 hgdata1/elastalert:b846d3461eb1 "./trap.sh" 47 minutes ago Up 43 minutes elastalert
20b45a285e46 hgdata1/beats:b846d3461eb1 "./trap.sh" 47 minutes ago Restarting (7) 14 minutes ago httpd-beat-packet
8765d32780c2 hgdata1/beats:b846d3461eb1 "./trap.sh" 47 minutes ago Restarting (7) 14 minutes ago mysql-beat-packet
df39c284be48 hgdata1/beats:b846d3461eb1 "./trap.sh" 47 minutes ago Restarting (7) 14 minutes ago beat-topbeat_httpd_bearfist
bc9e517f4e57 hgdata1/ui:88a1a097c407 "./trap.sh" About an hour ago Up 43 minutes 8000/tcp admin-a1
550953ac7e21 hgdata1/ui:88a1a097c407 "./trap.sh" About an hour ago Exited (0) About an hour ago admin-a1_previous_2
afe6d33b92ba f06503660e96 "/bin/sh -c ./trap.sh" About an hour ago Exited (0) 18 minutes ago focus-v7_previous_2
276bf2f70b31 hgdata1/kibana:a99520a05c03 "./trap.sh" About an hour ago Up 43 minutes 5601/tcp kibana
883d813cb85e hgdata1/logstash:a99520a05c03 "./trap.sh" About an hour ago Up 43 minutes logstash
62fbfcdb9b70 hgdata1/elasticsearch:a99520a05c03 "./trap.sh" About an hour ago Exited (128) 45 minutes ago es
0e982a0ba0e3 hgdata1/ldap_bearfist:16a8e5192c02 "./trap.sh" About an hour ago Up 43 minutes ldap-bearfist-v7
db2607fda9d8 hgdata1/api:16a8e5192c02 "./trap.sh" About an hour ago Up 43 minutes api-bearfist-v7
62742daaba39 hgdata1/persistence:16a8e5192c02 "/bin/sh -c 'sudo /tr" About an hour ago Up 43 minutes 3306/tcp db-bearfist-v7
433a6f77f1da hgdata1/httpd:16a8e5192c02 "./trap.sh" About an hour ago Up 43 minutes 0.0.0.0:443->443/tcp httpd
e4a758e6f86a hgdata1/ldap_admin:16a8e5192c02 "./trap.sh" About an hour ago Up 43 minutes ldap-admin-a1
e60803dcbb63 hgdata1/api:16a8e5192c02 "./trap.sh" About an hour ago Up 43 minutes api-admin-a1
4bcb5c831d03 hgdata1/api:16a8e5192c02 "./trap.sh" About an hour ago Up 43 minutes api-ops-o1
892a71544263 hgdata1/modsecurity:60be76623f1f "./trap.sh" About an hour ago Exited (0) About an hour ago modsecurity
$ sudo docker inspect es
[
{
"Id": "62fbfcdb9b7000113391d5a5427ae90b37b0c54252ff5c05a4dc2d9b0e4d4447",
"Created": "2016-02-17T13:24:50.575290212Z",
"Path": "./trap.sh",
"Args": [],
"State": {
"Status": "exited",
"Running": false,
"Paused": false,
"Restarting": false,
"OOMKilled": false,
"Dead": false,
"Pid": 0,
"ExitCode": 128,
"Error": "service endpoint with name es already exists",
"StartedAt": "2016-02-17T13:44:29.646211683Z",
"FinishedAt": "2016-02-17T14:11:26.649051684Z"
},
"Image": "sha256:820bc8ede34a6d1d657188b28a3ab1ea9eedc248e94747ed001dc2d5c2caf18b",
"ResolvConfPath": "/home/seb/hgdata/deployments/docker/containers/62fbfcdb9b7000113391d5a5427ae90b37b0c54252ff5c05a4dc2d9b0e4d4447/resolv.conf",
"HostnamePath": "/home/seb/hgdata/deployments/docker/containers/62fbfcdb9b7000113391d5a5427ae90b37b0c54252ff5c05a4dc2d9b0e4d4447/hostname",
"HostsPath": "/home/seb/hgdata/deployments/docker/containers/62fbfcdb9b7000113391d5a5427ae90b37b0c54252ff5c05a4dc2d9b0e4d4447/hosts",
"LogPath": "/home/seb/hgdata/deployments/docker/containers/62fbfcdb9b7000113391d5a5427ae90b37b0c54252ff5c05a4dc2d9b0e4d4447/62fbfcdb9b7000113391d5a5427ae90b37b0c54252ff5c05a4dc2d9b0e4d4447-json.log",
"Name": "/es",
"RestartCount": 0,
"Driver": "overlay",
"MountLabel": "",
"ProcessLabel": "",
"AppArmorProfile": "",
"ExecIDs": null,
"HostConfig": {
"Binds": [
"/home/seb/hgdata/deployments/elk/elasticsearch:/home/elasticsearch:rw"
],
"ContainerIDFile": "",
"LogConfig": {
"Type": "json-file",
"Config": {}
},
"NetworkMode": "backbone2",
"PortBindings": null,
"RestartPolicy": {
"Name": "unless-stopped",
"MaximumRetryCount": 0
},
"VolumeDriver": "",
"VolumesFrom": [],
"CapAdd": null,
"CapDrop": null,
"Dns": [],
"DnsOptions": [],
"DnsSearch": [],
"ExtraHosts": null,
"GroupAdd": null,
"IpcMode": "",
"Links": null,
"OomScoreAdj": 0,
"PidMode": "",
"Privileged": false,
"PublishAllPorts": false,
"ReadonlyRootfs": false,
"SecurityOpt": null,
"UTSMode": "",
"ShmSize": 67108864,
"ConsoleSize": [
0,
0
],
"Isolation": "",
"CpuShares": 0,
"CgroupParent": "",
"BlkioWeight": 0,
"BlkioWeightDevice": null,
"BlkioDeviceReadBps": null,
"BlkioDeviceWriteBps": null,
"BlkioDeviceReadIOps": null,
"BlkioDeviceWriteIOps": null,
"CpuPeriod": 0,
"CpuQuota": 0,
"CpusetCpus": "",
"CpusetMems": "",
"Devices": null,
"KernelMemory": 0,
"Memory": 0,
"MemoryReservation": 0,
"MemorySwap": 0,
"MemorySwappiness": -1,
"OomKillDisable": false,
"PidsLimit": 0,
"Ulimits": null
},
"GraphDriver": {
"Name": "overlay",
"Data": {
"LowerDir": "/home/seb/hgdata/deployments/docker/overlay/e9bcae64c4da4f3d74006d6795801044340461f3479ef6af1e2dddf2af1b4404/root",
"MergedDir": "/home/seb/hgdata/deployments/docker/overlay/0a92bf5594a6701a2557a9e39585ecbc337fd04326c2935b73edb91e2086c2dd/merged",
"UpperDir": "/home/seb/hgdata/deployments/docker/overlay/0a92bf5594a6701a2557a9e39585ecbc337fd04326c2935b73edb91e2086c2dd/upper",
"WorkDir": "/home/seb/hgdata/deployments/docker/overlay/0a92bf5594a6701a2557a9e39585ecbc337fd04326c2935b73edb91e2086c2dd/work"
}
},
"Mounts": [
{
"Source": "/home/seb/hgdata/deployments/elk/elasticsearch",
"Destination": "/home/elasticsearch",
"Mode": "rw",
"RW": true,
"Propagation": "rprivate"
}
],
"Config": {
"Hostname": "62fbfcdb9b70",
"Domainname": "",
"User": "elasticsearch",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"ExposedPorts": {
"9200/tcp": {},
"9300/tcp": {}
},
"Tty": true,
"OpenStdin": false,
"StdinOnce": false,
"Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
],
"Cmd": [
"./trap.sh"
],
"Image": "hgdata1/elasticsearch:a99520a05c03",
"Volumes": null,
"WorkingDir": "",
"Entrypoint": null,
"OnBuild": null,
"Labels": {}
},
"NetworkSettings": {
"Bridge": "",
"SandboxID": "7bca83422a8c4d24e9eb786262bd0368802dd3f2693343d0431ffaeb1614f098",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": null,
"SandboxKey": "/var/run/docker/netns/7bca83422a8c",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"MacAddress": "",
"Networks": {
"backbone2": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"NetworkID": "38a2aa06eb3bae5f48b988f7a9cf7950b5cc6798243554da1f38b5f53b9fcffd",
"EndpointID": "",
"Gateway": "",
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": ""
},
"bridge": {
"IPAMConfig": {},
"Links": null,
"Aliases": null,
"NetworkID": "0df17fcb288d7a4e9b77815f78388dfa494f16b35dffeb38122f92220bc61a99",
"EndpointID": "",
"Gateway": "",
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": ""
}
}
}
}
]
$ sudo docker start es
Error response from daemon: service endpoint with name es already exists
Error: failed to start containers: es