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 email@example.com.
Mary Hood Jul 29 • Announcements / Current System Status
Title: Portal (my.joyent.com) Issues
Incident Start Time: July 28, 2016 2:52 PM (UTC) 07:52 AM (PT)
Incident End Time: Ongoing
API's Affected: N/A
Portal Affected: Yes
Customer VM's affected: No
Description: Users are experiencing slow response while logging into the portal as well as some authorization errors.
This issue has been mitigated for the time being. A fix will be forthcoming in the next few days. Until then, portal users may experience slowness logging into portal. Your patience and understanding is much appreciated.
Sean G. Jun 28 • Announcements / Security Advisories
New releases of the Node.js packages have been added to the 2016Q1 pkgsrc repository. The following latest package releases address the vulnerabilities outlined in this notice:
If you are running on a SmartOS image that is using a different pkgsrc repository, you can still install the above by using the following command (you may want to first test for any potential incompatibilities on a non-production machine):
$ pkg_add http://pkgsrc.joyent.com/packages/SmartOS/2014Q4/x86_64/All/<nodejs_package>
You can visit this Node.js page for more information about these vulnerabilities.
Triton Cloud Users
The public cloud has been fixed; customers are advised to update their individual instances with the relevant Node.js packages.
Triton Enterprise Users
We will update this notice as soon as the 20160625 and 20160707 releases become available via the support channel, so that software customers can update their installations.
Please check the notices applicable to the Linux Distro you are using for the necessary remedial actions:
This notice is to advise all Triton Cloud (public cloud) and Triton Enterprise software (formerly SDC) customers of the following recently-identified Node.js security vulnerabilities:
Zone::Newfunction. This could potentially be used to cause a Denial of Service via buffer overflow or as a trigger for a remote code execution; mitigation will be required.
For now, you can visit this Node.js page to obtain additional details. Within the next several days, Joyent will proactively update this notice to confirm actions that we have taken, as well as provide specific details on any required actions to be taken by both Triton Cloud and Triton Enterprise customers to mitigate CVE-2016-1669. Your attention is appreciated.
Sean G. May 27 • Announcements / Current System Status
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.
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:
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.
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 firstname.lastname@example.org.
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
in this case, for httpd, that would be
Create a file named override.conf in that directory, i.e.:
Edit that file to contain
The service should now start properly.