To stay updated with announcements regarding incidents and maintenance please visit or status page at status.joyent.com.
You can subscribe for automatic notifications when new incidents occur and maintenances are scheduled. In general maintenance events are ONLY published on the status page.
To submit a support request please login or send us an email at email@example.com.
Sean G. Aug 24 • Announcements / Announcements
Joyent is excited to announce a new version of the software image used for Manta compute jobs. The new image is based on the 64-bit LTS version of the 16.1.0 base image, which includes upgraded versions of the packages already available in Manta.
The new image will become the default for new jobs, starting 19-September-2016. While we are confident that this new image will be a compatible upgrade for most customers, it is possible that some applications could break due to the upgrade. For this reason, it is strongly recommended that you test existing jobs on the new image *prior* to September 19th:
If you need any assistance, please contact Support.
Manta compute jobs run inside containers known as compute zones. Each zone is created from a software image that defines which software packages will be available and installed in that zone.
Previously, new Manta jobs were executed in zones based on the SmartOS 13.3 base image. Starting today, new jobs can instead choose to run in zones based on the 16.1.0 base image. The new image includes more choices in software, and offers newer versions for many of the existing packages.
It is important to note that the image defines which pkgsrc packages are installed in the zone. However, you can always run your own software in a zone based on any image, as long as you provide all of your own dependencies and/or rely only on libraries that do not alter incompatibilities over time.
Since the 13.3-based 32-bit image is still the current default, there is no immediate change for users unless you opt in to use the new image. However, starting on September 19, all jobs will run in the 16.1-based 64-bit image by default. For that reason, it is strongly recommended that you test your jobs on the 16.1-based image as soon as possible, to avoid any potential issues when the new image is deployed.
You can try the new image today by adding --image=16.1 to your mjob command. You have to do this for each phase.
$ mjob create \
--image=16.1 -m "grep request_id" \
--image=16.1 -r "sort | uniq -c"
You can also experiment with the image using mlogin as follows:
$ mlogin --image=16.1
We understand that some users may need to keep using the old 13.3-based image after we switch the default to the 16.1 version. We will retain the old image in a small subset of zones, but capacity will be significantly reduced. The old image will be completely removed in the near future, and we will provide further notice when that has been scheduled.
To explicitly choose the old image, the instructions shown above for the new image apply, except that you will want to substitute the (following) old image version for the new one:
mjob create --image=13.3
Again, if you need further help moving to the new image (after reading the information above), please contact Joyent Support.
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.