Is it possible to correctly shutdown a openbsd 4.7 or 4.9 with
virsh shutdown OpenBSD
The openbsd is under kvm/qemu configured from libvirt.
shutdown should send an ACPI signal "Power button pressed", but my openbsd guest does not react to this.
Also, can I configure OpenBSD to really turn off power of virtual machine when doing halt? Now it asks user from console "press any key to reboot" and don't switch power off.
did you try?
# shutdown -hp now
I did that in my openbsd machine, logged through ssh and it works fine. The machine is shutdown and virsh shows that too.
virsh # list --all
Id Name State
----------------------------------
- CentOS_6 shut off
- openbsd shut off
Hope it helps.
You can use "halt -p" to power down the VM after the OS is halted.
I have not been able to get OpenBSD 4.7 or 4.9 to respond to ACPI signals on KVM/QEMU that ships with Ubuntu Jaunty (9.04).
There's neither paravirt driver nor agent (qemu guest agent) in OpenBSD. But see acpibtn(4), it states if a value is set via sysctl it would react to acpi call.
Related
Trying to install Gerrit on a Mac that has also Jenkins installed. So far:
Installed MySQL via Brew successfully.
Added user & db for Gerrit to MySQL.
D/l of gerrit.war from https://gerrit-releases.storage.googleapis.com/index.html
Installed gerrit.war into ~/Applications/Gerrit
Set canonicalWebUrl to http://localhost:8080/gerrit/ in gerrit.config
Restart Gerrit with ~/Applications/Gerrit/bin/gerrit.sh restart
But restart fails. There seems to be no consistent Mac Gerrit setup guide whatsoever and I feel I'm stuck with this issue.
Gerrit error_log says:
ERROR com.google.gerrit.pgm.Daemon : Unable to start daemon
java.lang.IllegalStateException: Cannot start HTTP daemon
Has anyone running this config on a Mac and can give me some help?
on a Mac that has also Jenkins installed
Most likely the cause is that Jenkins is already running on the same port (8080). Try to change Gerrit's canonicalWebUrl to another port (or change Jenkins' port).
I am learning laravel 5.4 "queues" chapter. I have a problem about queue:restart command. Because when I test it on my windows 10 platform, I found this command seems just kill queue worker, but not restart worker. So I wonder whether this command does not work on windows or this command is just kill worker but not restart worker? Thanks.
The queue:restart command never actually restarts a worker, it just tells it to shutdown. It is supposed to be combined with a process manager like supervisor that will restart the process when it quits. This also happens when queue:work hits the configured memory limits.
To keep the queue:work process running permanently in the background, you should use a process monitor such as Supervisor to ensure that the queue worker does not stop running.
Source: https://laravel.com/docs/5.4/queues#running-the-queue-worker
I am using Bluemix container service and am unable to do cf ic login from behind a firewall, even though I have configured proxies.
When I do
cf ic -v login
I get the error message:
Authenticating with the IBM Containers registry host
registry.ng.bluemix.net... FAILED The attempt to authenticate with the
IBM Containers registry host registry.ng.bluemix.net was unsuccessful.
****Warning: '-e' is deprecated, it will be removed soon. See usage. Error response from daemon: Get
https://registry.ng.bluemix.net/v1/users/: dial tcp
198.23.117.106:443: i/o timeout
To test that my proxy is configured, I do this:
wget https://registry.ng.bluemix.net/v1/users/
--2016-10-25 11:25:23-- https://registry.ng.bluemix.net/v1/users/ Resolving proxy-chain.intel.com (proxy-chain.intel.com)... 10.19.8.225
Connecting to proxy-chain.intel.com
(proxy-chain.intel.com)|10.19.8.225|:912... connected. Proxy request
sent, awaiting response... 404 Not Found 2016-10-25 11:25:24 ERROR
404: Not Found.
If I disconnect VPN so I no longer have a firewall and need a proxy, and unset my proxies, it works.
These are the proxies I have set:
printenv | grep -i proxy
http_proxy=http://proxy-chain.intel.com:911
ftp_proxy=http://proxy-chain.intel.com:911
socks_proxy=http://proxy-chain.intel.com:1080
https_proxy=http://proxy-chain.intel.com:912
no_proxy=intel.com,.intel.com,10.0.0.0/8,192.168.0.0/16,localhost,127.0.0.0/8,134.134.0.0/16
>
More experiments:
When I set the proxy to something bogus, it fails immediately:
> export https_proxy=http://foobarsfsdf.com
> cf ic login
FAILED
auth request failed: Error performing request: Post https://login.ng.bluemix.net/UAALoginServerWAR/oauth/token: http: error connecting to proxy http://foobarsfsdf.com: dial tcp: lookup foobarsfsdf.com on 10.0.2.3:53: no such host
>
When I set the proxy correctly, it fails later:
> cf ic login
Deleting old configuration file...
Retrieving client certificates for IBM Containers...
Storing client certificates in /home/rscohn1/.ice/certs/...
Storing client certificates in /home/rscohn1/.ice/certs/containers-api.ng.bluemix.net/80cc2e8c-4df0-4700-bd04-77f2e8777f80...
OK
The client certificates were retrieved.
Checking local Docker configuration...
OK
Authenticating with the IBM Containers registry host registry.ng.bluemix.net...
FAILED
The attempt to authenticate with the IBM Containers registry host registry.ng.bluemix.net was unsuccessful.
****Warning: '-e' is deprecated, it will be removed soon. See usage.
Error response from daemon: Get https://registry.ng.bluemix.net/v1/users/: dial tcp 198.23.117.106:443: i/o timeout
When you are not connected to the IBM Containers registry host, you can run only a limited number of IBM Containers commands. Check the spelling of the host URL and try again. If the host URL is correct, open a new command line or terminal window before retrying.
It looks like some parts of the ic plugin uses proxies, and some parts do not.
You need to add the proxy on to your Docker daemon configuration. Also note that as Alex says, you should make sure to configure a HTTPS proxy.
See here for some information on how to do that with Systemd on Linux (Ubuntu 16.04+): https://docs.docker.com/engine/admin/systemd/#http-proxy
For older Linux distributions, such as Ubuntu versions before 16.04, Docker uses Upstart. You'll find the Upstart configuration file at /etc/default/docker, with a sample of how to set the proxy up in comments inside that file.
If you're using the Docker for Mac or Docker for Windows apps, you'll find the proxy configuration options in Preferences -> Advanced.
Make sure to restart Docker after changing the configuration, so that your changes take effect. On Linux: sudo service docker restart. On Mac or Windows, right-click the Docker icon and click restart.
I can't get the Apache service to start.
When I try to start it from services I get the following events in event viewer.
The Apache service named reported the following error: (OS
10048)Only one usage of each socket address (protocol/network
address/port) is normally permitted. : AH00072: make_sock: could not
bind to address 0.0.0.0:8090
AH00451: no listening sockets available, shutting down .
AH00015: Unable to open logs
.
I've tried port 80 port 8080 and 8090 and I'm getting the same errors.
I've checked to see if these ports are in use and they are not listed through netstat or through a currports.exe I've used.
I had everything running but I did a SYMLINKS rebuild on apache and mysql and I think I may have done them too quick as I got an error message at the time and mysql and apache stayed down.
I had to re-install the mysql service but the Apache service is going nowhere!!
I have wamp 2.5 with apache 2.4.9 running on windows 2008 R2 Enterprise for the purpose of an office intranet using wordpress.
Help very much appreciated
Cheers
JCro
EDIT Code from Httd.conf. I have just added the lines I've amended #
#
Listen 12.34.56.78:80
Listen 0.0.0.0:80
Listen 80
#
# Dynamic Shared Object (DSO) Support
#
#
ServerName localhost:80
HostnameLookups Off
#
Its not too clear what caused this situation but this may get you back up and running.
Start WAMPServer
uninstall the Apache service
wampmanager -> Apache -> Service -> Remove Service
reinstall the Apache service
wampmanager -> Apache -> Service -> Install Service
start Apache
wampmanager -> Apache -> Service -> Start/Resume Service
Now if you ever want to rebuild the Apache SYMLINKS (mysql has non by default) you do this :-
wampmanager -> Apache -> Version -> (click on the current version number)
Then wait a few seconds while WAMPServer rebuilds the SYMLINKS and restarts Apache for you.
Oh then I would put Apache back to Listen on port 80.
RE: Your httpd.conf amendments
This line should be a comment, its an example but not intended to be part of the used parameters in this file
#Listen 12.34.56.78:80
These 2 lines shoud be
# this is for IPV4
Listen 0.0.0.0:80
# This is for IPV6
Listen [::0]:80
These 2 lines look ok as
ServerName localhost:80
HostnameLookups Off
How to see port number in Windows 10?
Open a command prompt window (as Administrator) From "Start\Search box" Enter "cmd" then right-click on "cmd.exe" and select "Run as Administrator"
Enter the following text then hit Enter. netstat -abno. ...
Find the Port that you are listening on under "Local Address"
Look at the process name directly under that.
After you found the PID of the service running on a given your computer, open your task Manager and sort the running processes by PID. find your target PID right click and go to services, right click on the service and stop the service. without starting your apache 2.4 service just start by getting this path "C:\Apache24\bin>httpd -k start" then enter. This is the way I become successful after many ups and down.
OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address [::]:80 (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address 0.0.0.0:80 AH00451: no listening sockets available, shutting down AH00015: Unable to open logs
I was getting the same error when i tried to start the Apache2.4. But when i replaced the Listen 80 with Listen 8080(by going to httpd.conf file placed in conf folder inside Apache24 folder), my problem solved.
you may still get the complaint about port 443. If you look through the httpd.conf, you won’t be able to find 443. But, you will find the following:
Secure (SSL/TLS) connections
Include “conf/extra/httpd-ssl.conf”
Look in the httpd-ssl.conf file, and replace 443 with some other port.
Enjoy!
Is there any way to start a service and force a service that is already running to stop if it uses the port that the service I want to start is going to be using?
I'm going to be installing apache and mysql, and want the services to be running without having to manually stopping existing services that use port 80/3306 such as existing apache/mysql services.
I'm using NSIS to make my installer.
To find the process listening on port 80 perhaps you could do the equivilent of this from the command line:
c:\>netstat -aon | findstr 0.0:80
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 3488
3488 is the process id. Not sure what APIs netstat is using though.
Without disabling or reconfiguring the service that is already using the desired port is still going to cause problems on system restart. The best bet might be to abort the install if the port is already in use. To check if a port is in use, use this NSIS TCP plugin.