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

Ryan Sep 1 Announcements / Announcements

Recent updates to the procps package in CentOS have caused issues with some utilities on container-native images (namely ps, top and related tools from the procps package). This can manifest either after a yum update or upon provisioning the latest images. 

If you encounter this, an immediate workaround is to upload the attached procps-3.2.8-30.el6.x86_64.rpm to affected machines and run:

 

rpm -i --force procps-3.2.8-30.el6.x86_64.rpm

 

or to grab the attachment directly from this post:

 

rpm -i --force "https://help.joyent.com/attachments/token/d9YrOO37f4Xdj2xOym4pY5vHi/?name=procps-3.2.8-30.el6.x86_64.rpm"

Afterwards you'll want to exclude the procps package from updates for the time being either by running 

yum update ---exclude=procps*

when updating or by adding the following line to /etc/yum.conf:

exclude=procps*

 

 

 

Elizabeth Aug 26 Announcements / Incidents & Notifications

FINAL UPDATE as of 17:05 on 1-Sept-2015 PDT (00:05 on 2-Sept-2015 UTC)

This maintenance has been completed in all data centers.

UPDATE as of 12:30 on 1-Sept-2015 PDT (19:30 UTC): 

The API update window for the EU-AMS-1 data center started at 12:00 PDT (19:00 UTC), rather than the 13:00 PDT (20:00 UTC) start time previously posted. We apologize for the late notice on this change.

The API updates to the other data centers are (still) scheduled to begin at the times shown below.

We have scheduled API service updates in all of our data centers for this upcoming Tuesday, 1-September-2015. The expected duration of impact is approximately 60 minutes per data center, and the scheduled start times for each data center are outlined as follows:

  • EU-AMS-1: 12:00 PDT 1-Sep-2015 (19:00 UTC 1-Sep-2015)  Completed as of 12:30 PDT (19:30 UTC)

  • US-EAST-3: 13:45 PDT 1-Sep-2015 (20:45 UTC 1-Sep-2015)  Completed as of 14:05 PDT (21:05 UTC)

  • US-EAST-2: 14:30 PDT 1-Sep-2015 (21:30 UTC 1-Sep-2015)  Completed as of 14:50 PDT (21:50 UTC)

  • US-EAST-1: 15:15 PDT 1-Sep-2015 (22:15 UTC 1-Sep-2015)  Completed as of 16:00 PDT (23:00 UTC)

  • US-SW-1: 16:00 PDT 1-Sep-2015 (23:00 UTC 1-Sep-2015)  Completed as of 16:45 PDT (23:45 UTC)

  • US-WEST-1: 16:45 PDT 1-Sep-2015 (23:45 UTC 1-Sep-2015)  Completed 17:05 1-Sept-2015 PDT (00:05 2-Sept-2015 UTC)

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.

Elizabeth Aug 17 Announcements / Announcements

Due to a change made by one of our network providers, we have identified an issue with an entry that may exist in the /etc/resolv.conf file of your instance(s) -- an entry which specifies a name server that no longer works. To prevent potential networking issues, we suggest that you check your /etc/resolv.conf file for the following entry:

nameserver 216.52.1.1 

If the above entry exists, please remove it or comment it out. Going forward, this issue will not be seen on newly-provisioned instances.

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.

Ryan Jul 25 Announcements / Incidents & Notifications

UPDATE: If you encounter this issue and require further assistance, please contact Joyent Support by submitting a request at the support portal or by emailing support@joyent.com.

Engineering is investigating an issue where updated or newly-added machine tags are not showing via the API or the customer portal

We will update as soon as we have further information. 

Sean G. Jul 14 Announcements / Announcements

Introduction

This advisory describes the scope of the recently-announced, "high-severity" OpenSSL vulnerability classified as CVE-2015-1793. This vulnerability could allow "man-in-the-middle" attackers to impersonate HTTPS servers and snoop on encrypted traffic.

Described in the sections below are actions being taken by Joyent, and actions recommended for customers to take. This article is meant to be used in addition to our 18-June-2015 and 20-March-2015 advisories regarding previously-announced OpenSSL vulnerabilities.

1) Upgrading your own OpenSSL version 1.0.2b, 1.0.2c, 1.0.1n or 1.0.1o

Should customers choose to address this vulnerability by upgrading OpenSSL on their own, they are advised to upgrade as follows:

  • OpenSSL 1.0.2b and 1.0.2c users should upgrade to 1.0.2d

  • OpenSSL 1.0.1n and 1.0.1o users should upgrade to 1.0.1p

Joyent customers can address this and other recently-announced vulnerabilities by re-installing OpenSSL with the following command:
pkgin -y up && pkgin -y in openssl 

2) Joyent-delivered software

CVE-2015-1793 and other vulnerabilities have been addressed in the most-currently-released versions of Joyent's software and package repositories:

  • pkgin repository 2015Q2 (openssl-1.0.2d)
  • pkgin repository 2015Q1 (openssl-1.0.2d)
  • pkgin repository 2014Q4 (openssl-1.0.1p)

  • pkgin respository 2014Q2 (openssl-1.0.1p)

  • SmartDataCenter (SDC): The fix for this vulnerability is available in any platform image after 20150709.

3) Linux users

For any necessary remedial actions, please check the notices applicable to the Linux distro you are using:

4) Further questions

As before, please be assured that Joyent's HTTPS endpoints for Manta, CloudAPI and our customer portal are not vulnerable.

Joyent customers who are using third-party operating systems are advised to contact their respective service providers for further information and instructions.

If you have followed the instructions above and further questions arise regarding mitigation of OpenSSL vulnerabilities (in Joyent products and services): Please contact Joyent Support by submitting a request at the support portal or by emailing support@joyent.com.

 

Overview | Recent