VMware Cloud Community
nettech1
Expert
Expert
Jump to solution

503 Service Unavailable vCenter 6.7.4000

I am getting the error below when trying to connect to vcsa 6.7, however I am able to connect to the Appliance Management where I see an alert for /storage/seat

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x00007fe9380182b0] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)

seat.png

Would this be a good solution to follow

vCenter Server Appliance Crash due to Full /Storage/SEAT Partition

or this ?

https://www.virtualizationhowto.com/2017/08/vmware-vcsa-6-5-upgrade-no-tiny-small-option/

Thanks

1 Solution

Accepted Solutions
4 Replies
Vijay2027
Expert
Expert
Jump to solution

Known issue: VMware Knowledge Base

nettech1
Expert
Expert
Jump to solution

VCDB=# SELECT nspname || '.' || relname AS "relation", pg_size_pretty(pg_total_relation_size(C.oid)) AS "total_size"

VCDB-#               FROM pg_class C

VCDB-#               LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace)

VCDB-#               WHERE nspname NOT IN ('pg_catalog', 'information_schema')

VCDB-#               AND C.relkind <> 'i'

VCDB-#               AND nspname !~ '^pg_toast'

VCDB-#               ORDER BY pg_total_relation_size(C.oid) DESC

VCDB-#               LIMIT 20;

      relation       | total_size

---------------------+------------

vc.vpx_event_arg_68 | 253 MB

vc.vpx_event_arg_67 | 253 MB

vc.vpx_event_arg_66 | 250 MB

vc.vpx_event_arg_69 | 249 MB

vc.vpx_event_arg_70 | 246 MB

vc.vpx_event_arg_65 | 246 MB

vc.vpx_event_arg_71 | 246 MB

vc.vpx_event_arg_72 | 245 MB

vc.vpx_event_arg_64 | 241 MB

vc.vpx_event_arg_60 | 240 MB

vc.vpx_event_arg_73 | 240 MB

vc.vpx_event_arg_61 | 239 MB

vc.vpx_event_arg_83 | 239 MB

vc.vpx_event_arg_82 | 237 MB

vc.vpx_event_arg_77 | 237 MB

vc.vpx_event_arg_63 | 236 MB

vc.vpx_event_arg_79 | 236 MB

vc.vpx_event_arg_81 | 236 MB

vc.vpx_event_arg_75 | 235 MB

vc.vpx_event_arg_78 | 235 MB

(20 rows)

0 Kudos
nettech1
Expert
Expert
Jump to solution

Is the issue resolved in 14320388 build ?

0 Kudos
berndweyand
Expert
Expert
Jump to solution

no - issue is resolved in Build 15018017 - released yesterday.

tested today on one host - and it´s fine

0 Kudos