A general system error occurred connection refused

General system error occurred connection refused

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I have just build a VM in my ESXi 6 server and when I want to power it on, it’s throwing error as ‘A general system error occurred: connection refused’

Please see attached screenshot.

Help is appreciated.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Hope you have access to vCenter Appliance, Try restarting this «VMware vCenter workflow manager service»

To resolve this issue, start the VMware vCenter workflow manager service.

Windows vCenter Server

1. On the server that runs vCenter Server, open Start > Run , type services.msc and press Enter .
2. Right-click VMware vCenter workflow manager service and click start.
3. Attempt to power on the virtual machine again.

vCenter Server Appliance (VCSA)

1. Connect to the VCSA shell as root. For more information, see:

Run this command to restart the VMware vCenter workflow service ( vmware-vpx-workflow

# service vmware-vpx-workflow restart

Источник

General system error occurred connection refused

Если у вас не работает один из способов авторизации, сконвертируйте свой аккаунт по ссылке

Авторизуясь в LiveJournal с помощью стороннего сервиса вы принимаете условия Пользовательского соглашения LiveJournal

• Май 2022

1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30	31

Проблема: виртуальные машины vmware не включаются через стандартный интерфейс VCenter (ни в веб-интерфейсе, ни через VMWare vSphere Client). Процесс обрывается с ошибкой: «General system error occurred: connection refused».

Проблема заключается в остановке службы VMware vCenter Workflow Manager. Чтобы запустить её, соединяемся по ssh к VCenter Server Appliance, естественно под рутом и вводим команды:

shell.set —enabled true // активируем shell
shell // запускаем shell
service-control —status vmware-vpx-workflow // убеждаемся, что служба остановлена (статус stopped)
service-control —start vmware-vpx-workflow // запускаем службу

У меня на этом этапе служба запускаться отказалась. Поиски показали, что виной тому переполнение /storage/log. (проверить можно с помощью df -vh). На это vmware предлагает следующее решение.

После этого служба vmware-vpx-workflow запустилась и проблема была решена.

What you can do is delete the log files that are currently there. If you haven’t changed your root password after 30 days (or maybe 60), the cron job won’t clear/rotate log files.

How to check and fix it. Connect via putty or direct console to your vcsa (vCenter)

1)Run du -h (or «du -h —max-depth=0 * | sort -hr» to sort it a bit) you’ll see how much space is used in each of your drives.

2) Identify the directories that are at 100% usage, you’ll probably notice either /dev/sda3 (Which is /) and/or /dev/mapper/log_vg-log (Which is /storage/log)

Источник

StorageGumbo

Thursday, November 5, 2015

Cannot Start a VM — A general system error occurred: Connection refused

The error referenced in the title was one I ran into today while trying to start some VMs. I finally found a KB somewhat related to this issue and the workaround did the trick for me.

Basically, the vCenter Workflow Manager service had stopped on my vCenter server. In my case, I’m running the 6.0.0 vApp so I had to open an SSH session and enter the following:

shell.set —enabled true
shell
service-control —status vmware-vpx-workflow
(this command confirmed the service was stopped)
service-control —start vmware-vpx-workflow

Once running, I was able to start VMs again from vCenter.

Not sure why this was so hard to find in a web search but hopefully the search engines will pick up this blog post and save people some time!

Thanks! This worked for me although I had a different issue but same symptom. vmware-vpx-work service was already running so I checked the logs and for some reason, vcenter was attempting to connect to localhost instead of wsxhost when powering on. Restarted the service and its now connecting to the correct host.

Thank you for posting this! This was exactly what I needed

Источник

A general system error occurred connection refused

A general system error occurred: Authorize Exception в VMware vCenter 5.X.X.

Вот как выглядит ошибка A general system error occurred-Authorize Exception в VMware vCenter, небольшое окно с предупреждением и сделать ничего нельзя, кроме как нажать ок.

Немного погугли смысл сводился к тому что служба SSO не может подцепиться к LDAP. Если кто не помнит, то SSO (Single Sign-On) мы устанавливали вместе с VMware VirtualCenter Server, в двух словах это некая база единой аутентификации, которую можно использовать во многих сервисах. Так у меня домен Active Directory, то логично, что мне было удобно раздавать права на объекты VMware VirtualCenter Server, через AD учетки.

Посмотрев еще логи в Windows, обнаружилось вот такое сообщение, что не получается соединиться с контроллером домена, Event ID 1000.

A general system error occurred-Authorize Exception в VMware vCenter 5.1-02

Как решается ошибка a general system error occurred

Заходим на vSphere Web Client https://hostname:9443, вы его так же ставили при установке VMware VirtualCenter Server.

Пытаемся ввести наши данные доменные, и конечно же он нас посылает)))

A general system error occurred-Authorize Exception в VMware vCenter 5.1-03

Но при установке мы заводили пользователя admin@system-domain и его пароль, помогут для входа, еще в качестве логина может подойти administrator@ vsphere.local

Идем в Administration > Configuration > identity Sources. Выбираем активное подключение к домену.

A general system error occurred-Authorize Exception в VMware vCenter 5.1-04

Смотрим что есть, в моем случае один криворукий админ поигрался с контроллером, поэтому старый коннект я удалил и сделал так

A general system error occurred-Authorize Exception в VMware vCenter 5.1-05

Так же можно выбрать от имени кого проверять требуется в некоторых случаях, и есть возможность с сертификатом сделать. Как более простой вариант можно использовать Integrated Windows Authentication, она позволяет подключиться к AD от имени учетной записи компьютера (он должен быть членом домена)

После чего нажмите кнопку использовать по умолчанию данное подключение. Вот так вот просто решается ошибка а general system error occurred: Authorize Exception в VMware vCenter 5.X.

Thursday, November 5, 2015

Cannot Start a VM — A general system error occurred: Connection refused

The error referenced in the title was one I ran into today while trying to start some VMs. I finally found a KB somewhat related to this issue and the workaround did the trick for me.

Basically, the vCenter Workflow Manager service had stopped on my vCenter server. In my case, I’m running the 6.0.0 vApp so I had to open an SSH session and enter the following:

shell.set —enabled true
shell
service-control —status vmware-vpx-workflow
(this command confirmed the service was stopped)
service-control —start vmware-vpx-workflow

Once running, I was able to start VMs again from vCenter.

Not sure why this was so hard to find in a web search but hopefully the search engines will pick up this blog post and save people some time!

Thanks! This worked for me although I had a different issue but same symptom. vmware-vpx-work service was already running so I checked the logs and for some reason, vcenter was attempting to connect to localhost instead of wsxhost when powering on. Restarted the service and its now connecting to the correct host.

«Virtual Roads. Actual Clouds»

Pages

Translate

Total Pageviews

My YouTube Channel

Thursday, 28 January 2016

Unable to Power on VM in vCenter 6 — A general system error occurred: Connection refused

Issue:-
Today when i was trying to power on one of my VM in vSphere 6 Environment it’s getting failed with message «A general system error occurred: Connection refused».

Then i tried to power on this VM by directly connecting with my ESXi Host from vSphere Client and i was able to power on my vm then question was why i cannot start the same VM if i am connected with my ESXi host through vCenter. Then i found a KB article from VMware on How to start/stop the services in vCenter Server Appliance Version 6.

Reason:-
VMware vCenter Workflow Manager Service was Stopped.
1. To get in to vCSA 6.0 Shell
(a). I accessed my vCSA 6.0 through Putty
(b). Then to enable BASH access i executed this command
shell.set —enabled True
(c) Then to Launch BASH i executed this command
shell

service-control —status vmware-vpx-workflow

Solution:-
Start the VMware vCenter Workflow Manager Service

service-control —start vmware-vpx-workflow

After this i tried to Power On the VM again and i was able to power it on.

vCenter Server Appliance services:-

Источник

VMware vSphere: A general system error occurred: Connection refused When starting Virtual Machines.

I had an issue the other day with starting a VM. It would DRS successfully, however fail with “A general system error occurred: Connection refused”

Googling tells me that the culprit is the vmware-vpx-workflow service being stopped. I SSHed into my VCSA and sure enough found that the service was indeed stopped.

So I attempt starting the service, and that failed.

What the hell? Doing a tail on all the logs in the /var/log/vmware/workflow folder don’t come up with anything. However after re-reading the errors during start I realized…maybe its a disk space issue.

Sure enough, our log disk was full. I grew the log disk, and ran the autogrow command in VMware to resize the disks in the VCSA, restarted the services and VOLA!

After updating the disk size, we were all set and I was able to start VMs without issues.

Источник

Hello !

Little trouble yesterday when wanting to start a VM I encountered the following error: A general system error occurred: Connection refused

After a few minutes of research especially in the VMware KB I applied the few recommendations found :

Check the status of the vmware-vpx-workflow service in your vCenter console

First of all, check the status of the vmware-vpx-workflow service by logging in ssh to your vCenter appliance.

If the service is stopped, try restarting it:

If the service start fails with this error message:

There is a problem elsewhere.

Check used space of vCenter partitions

In my case the partition of log was full thus causing problems to generate the various logs necessary for the good operation of the vCenter.

To make some space, you can delete the logs of type “java_error12049.hprof”:

To go further, we can also reset to 0 the logs here:

and re-check the available disk space:

Cool cool! We have won some GB ! :).

Our service vmware-vpx-workflow is always stop I remind you!

By “security” and because there can be dependencies between services, it is better to stop all services and let VMware restart them in the right order, as is necessary. This has no impact on your production, it will just make access to the vSphere Client and vSphere Web Client console inaccessible.

If you are fast enough, you will see the start of the service scroll:):

We’re good, with an up & running service! 🙂

Managing Audit logs

We can go a little further. If like me, you have set a root password when installing VCenter, and you never came back on it then it may be expired. In fact, by default, the root password for the VCSA appliance expires every 365 days. If you don’t change it, then it collects a certain amount of error and makes the log audit bigger.

So at first you would have to change your root password if it has expired, or else make sure it does not expire. You can do this by connecting to this address:

• https://yourvcsa.tld:5480

Then we return to the VCenter in SSH and then restart the rotation of the logs that stopped at the end of the validity period of the password root.

Go check that the new logs of the day are well generated and archived:

If you ever have a log too big you can delete it or reset it to zero:

Hopefully it will have been helpful!

M.

Go further

Here some KB Vmware to go further in setting up the rotation of the logs:

• Log SSO
• CLOUDVM file Rotation-ram-size. Log

I had an issue where vMotion would no longer work. When selecting the target host in the vCenter UI, the compatibility check would fail with the error:

Error

A general system error occurred: Connection refused: The remote service is not running OR is overloaded, OR a firewall is rejecting connections.

Background

A Google search for the issue reveals quite a bit of possible causes, mostly pointing to several more standard causes, which were all in order. When digging deeper in the logs, I stumbled upon the same message appearing in /storage/log/vmware/vmware-vpxd/vpxd.log.

Continuing the search, someone mentioned that it could be caused by services not started, which can easily be revealed when logging into the VCSA through SSH, and running service-control —status —all from the command-line. That someone was right:

# service-control --status --all
Stopped:
 vmcam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-rbd-watchdog vmware-sps vmware-statsmonitor vmware-updatemgr vmware-vcha vsan-dps
Running:
 ...

Note: output truncated for readability

I compared the output to that of a «healthy» vCenter and noticed some services (vmware-sps and vmware-updatemgr) not started. Manually attempting to start the services did not help: the starting process kept hanging indefinitely. Looking into the logs of the service (/storage/logs/vmware-sps/sps.log) revealed another error (again, I truncated the output):

storage/logs/vmware-sps/sps.log

java.lang.IllegalStateException: Client initialization is not complete!

After some more searching, I came across this article which turned out to be the solution:

Certificates were updated and now SPS and update services will not start from vmware

The article stated that there’s an issue in the database: if there are multiple entries for the SSO admin account in a particular table (vpx_access), it would cause the vmware-sps service not to start.

And sure enough, although nothing was updated (no patches, no certificates), it turned out that there were indeed multiple entries for the SSO admin present in the database. After removing the surplus and restarting all services, all services could start properly and the issue was resolved.

Resolution

The steps I took to resolve the issue:

1. Enable shell access (more info)

2. Log on to the PostgreSQL database shell (more info):

   /opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres

3. Run the following query to check whether there are more than 1 SSO admin accounts present:

   SELECT * FROM vpx_access;

   Look for the entries for the SSO admin (for example: VSPHERE.LOCALAdministrator). You should get output similar to:

   VCDB=# SELECT * FROM vpx_access;
    id |          principal          | role_id | entity_id | flag | surr_key
   ----+-----------------------------+---------+-----------+------+----------
     1 | VSPHERE.LOCALAdministrator |      -1 |         1 |    1 |        1
   (1 row)

   If you see more than one row for the SSO admin, then there’s the issue. All rows, except the one with id = 1 should be removed.

4. Remove the extra rows where the principal = VSPHERE.LOCALAdministrator, leaving only the one with id = 1. Be careful how you construct your SQL query:

   DELETE FROM vpx_access WHERE principal = 'VSPHERE.LOCALAdministrator' AND id <> 1;

5. After running the query, re-run the SELECT statement to verify there’s only one account left.

6. Restart all services:

   service-control --stop --all
   service-control --start --all

   It will take some time to stop the services and start them again. Alternatively, you can also reboot the appliance.

After correcting the database, all services started without problems and functionality was restored.

Conclusion

If you get the particular error message mentioned at the start of this article, the solution presented here may not resolve it, but it’s worth checking before you move on to researching other possible causes.