Welcome to Joyent Cloud Customer Support

Stay updated with announcements, get answers from the community and share your feature suggestions with us.
You can also submit a request or send us an email at support@joyent.com.

 

Joyent Support

Sean G. May 27 Announcements / Current System Status

Overview

This notice is to alert our Joyent Public Cloud and Manta Storage Service customers to our newly enhanced maintenance/incidents notification system:

In making this change, our goal is to provide you (and all of our customers) with even faster, more user-tailored and efficient cloud-wide notifications about planned maintenance and unplanned incidents. This new notification system will allow us to reach that commitment.

Subscribing for Notifications

An important feature of our new notification system is that customers can subscribe to receive email notices of incidents and maintenance activities. In order to subscribe to these timely email alerts, follow these simple steps:

  1. Go to https://status.joyent.com and bookmark the page.
  2. While you are there, take a moment to click the "Subscribe" button in the top right corner, as illustrated below.
  3. You will be emailed a link that will let you easily manage the types of email alerts you wish to receive.

That’s all you need to do! Of course, you will also be able to view maintenance and incident notifications directly at https://status.joyent.com.

subscribe.png

Support

Thank you for your time in attending to this notice. If you are a Joyent customer and have any further questions regarding this change, please do not hesitate to submit a request via http://help.joyent.com or by email to support@joyent.com.

Ryan May 26 JoyentCloud Knowledge Articles / Virtual Machines

If you run into the following errors attempting to start services via systemctl in centos-7 or other systemd based infrastructure containers:

# systemctl start httpd
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.

 

Create a directory 

/etc/systemd/system/SERVICENAME.service.d/ 

in this case, for httpd, that would be 

/etc/systemd/system/httpd.service.d

Create a file named override.conf in that directory, i.e.:

/etc/systemd/system/httpd.service.d/override.conf

Edit that file to contain

[Service]
PrivateTmp=no

and run 

systemctl daemon-reload

The service should now start properly.

Elizabeth May 26 Announcements / Incidents & Notifications

This maintenance has been completed.

We have scheduled an emergency API service update to our US-SW-1 data center for today, 25-May-2016, starting at 23:15 UTC. The expected duration of impact is approximately 5 minutes.

Your ability to manage your instances via the API or through my.joyent.com will be limited during this time. Running instances will experience no impact other than orchestration (stopping/starting/destroying of VMs). We appreciate your patience and understanding, and will update this notice as soon as the maintenance is completed.

If you have any questions or concerns, please contact our Support team by raising a ticket at https://help.joyent.com or by email to support@joyent.com.

Andrew Hill May 23 Announcements / Incidents & Notifications

Update: This issue was resolved as of approximately 13:00 23-May-2016 UTC.

Incident Start Time (UTC): ~07:35 23-May-2016

Incident End Time (UTC): ~13:00 23-May-2016

Portal Affected: No

Customer Instances Affected: No

Description: Customers are currently unable to provision new Docker containers in the US-WEST-1 data center.

Andrew Hill May 23 Announcements / Incidents & Notifications

Incident Start Time: May 21 2016, 15:29 UTC (08:29 PDT)

Incident End Time: May 23 2016, 07:11 UTC 

API's Affected: imgapi

Portal Affected: No

Customer VM's affected: No

Description: Private cloud (on-prem) customers are unable to download images or image metadata.

 

Overview | Recent