All / Any

ActivePerl 5.6.1 Build 631 on a Windows 2012 server

We have been using ActivePerl 5.6.1 Build 631 for a particular home-grown application since 2002. At first it was on a Win NT server, but it was later put on a Win 2003. We now need to upgrade our server to Win 2012, but the 5.6.1 install does not complete successfully. Can we just install a later version without changing the Perl programs, or did the language evolve with the ActivePerl version?

Return Python output?

Hi,
Is there a way to return a result of a python program on the Command Output?
here is the problem:
I try to make a web application (tornado), but the problem is that i only see which links i used, but if i use a 'print something' on the code, i cant see the result of this variable.
Komodo Edit, version 8.5.4, build 14424, platform win32-x86. Built on Thu Aug 14 00:30:57 2014.

Stackato 3.4 Python-buildpack Update

Question: 

How can I update my Stackato Python Build-pack on my Stackato 3.4 VM?

Answer: 

In order to update the python build-pack on your Stackato 3.4 VM, follow the steps mentioned below:

1. Login to the Stackato 3.4 as an admin, to update the installed admin python-buildpack; ssh stackato@

2. Execute the below command
wget https://github.com/ActiveState/stackato-buildpack-python/archive/v2.90.1...

3. unzip v2.90.1.zip

4. cd stackato-buildpack-python-2.90.1

5. zip -rom9 v2.90.1.zip *

6. stackato update-buildpack --zip v2.90.1.zip python

7. cd ..

8. rm v2.90.1.zip

Note: Please do a stackato target and stackato login as an admin before running stackato update-buildpack command on the Stackato 3.4 node.

Contents of Batch Patch-30092014 - 3.4.1

Question: 

What fixes were included in the 3.4.1 batch patch-30092014?

Answer: 

This patch fixes the following issues, which are primarily internal:

- Removing noise from the fence logs
- Removing unnecessary fence tracebacks when obtaining memory and cpu usage
- Periodically removing rogue/orphaned Docker containers

Contents of Batch Patch-23092014-1 and Batch Patch-24092014-2 - 3.4.1

Question: 

What fixes were included in 3.4.1 batch patch-23092014-1, and patch-24092014-2?

Answer: 

These patches fix the following issues:

batch-patch-23092014-1
- API performance enhancements
- Bug deploying apps
- Bug deleting deployed apps
- Option for LDAP users to be assigned to dynamically generated space following their username. Users will be placed within personal organization and space with a configurable quota

batch-patch-24092014-2
- Typo `kato report --cluster`
- Bug OEM white label console customizations
- Bug deleting users from orgs
- Bug viewing applications

Ubuntu Security Updates

Question: 

How do I apply Ubuntu security updates to my Stackato cluster?

Answer: 

Ubuntu Security Updates

Both the Stackato VM and the Docker base image used for application containers run Ubuntu. To maintain an up-to-date system with all known security patches in place, the VM and Docker base images should be updated with the following process whenever an important security update becomes available in the Ubuntu repositories.

Upgrade the Stackato VM

Run the following commands on all cluster nodes, one node at a time:

sudo apt-get update
sudo unattended-upgrades -d

If you are using a proxy you may need to export http_proxy and https_proxy environment variables. For example:

sudo sh -c "http_proxy=http://myproxy.example.com:3128 https_proxy=http://myproxy.example.com:3128 unattended-upgrades -d"

This will run the unattended-upgrades script to install all upgrades from the "-security" stream.

Each node should be rebooted after unattended-upgrades completes to ensure new kernels, modules, and libraries are loaded.

2.10 - Patch the LXC Container Template

Follow the process laid out in this previous FAQ:
http://community.activestate.com/node/10406

3.X - Upgrade the Docker image

The base Docker image used for application containers should also be upgraded once the VM is up-to-date. Perform the following steps on each DEA node in the cluster, one node at a time:

Create a new working directory:

mkdir ~/upgrade-alsek && cd $_

Create a Dockerfile. In this new directory, create a file called "Dockerfile" and add the following:

FROM stackato/stack-alsek
RUN apt-get update
RUN unattended-upgrades -d
RUN apt-get clean && apt-get autoremove

Build the docker image. Give the image a tag relevant to this particular upgrade (e.g. "upgrade-2014-09-19"):

sudo docker build -rm -t stackato/stack-alsek:upgrade-2014-09-19 .

The "." at the end is important. It specifies to use the Dockerfile in the current directory.

Tag the Docker image as the "latest" stack-alsek image:

sudo docker tag stackato/stack-alsek:upgrade-2014-09-19 stackato/stack-alsek:latest

All running applications will need to be restarted by their owners or Stackato admins (using the management console or the stackato client) in order for security upgrades to take effect within their application containers. You can check which image running apps are using by running docker ps on your DEAs (but do not use docker restart).

If you have DEA autoscaling enabled, be sure to also update the DEA template

For more information, see the Stackato documentation:
docs.stackato.com/admin/best-practices/index.html#ubuntu-security-updates

Contents of Batch Patch-18092014 - 3.4.1

Question: 

What fixes were included in the 3.4.1 batch patch-18092014?

Answer: 

This patch fixes the following issues:

- Fix memory reporting from the stackato client. This impacts the "stackato stats" command on the client.
- Fix application to application communication in Stackato. Some applications could not communicate to other apps on the same cluster via port 80 or 443.
- Allows NFS to be mounted to application containers. Note that the application containers must be privileged.

Contents of Batch Patch-05082014 - 3.4.1

Question: 

What fixes were included in the 3.4.1 batch patch-05082014?

Answer: 

This patch included the following fixes:

-Fixed the way we read the autoscaling.yml file (/s/etc/autoscaling/autoscaling.yml) to allow us to properly set the security group(s) for autoscaled DEAs in EC2.
-Fixed cloud controller to properly allow deletion of applications for which the controller database has services which don't exist. The controller will now properly delete these applications rather than throwing an error.

Stackato 3.4 Patch: external-postgres-9.3

Question: 

What's in patch external-postgres-9.3?

Answer: 

external-postgres-9.3 allows the PostgreSQL data service to be compatible with an external PostgreSQL 9.3 instance. It was previously only compatible with PostgreSQL 9.1. This patch will restart PostgreSQL data service.

For more information on setting up an external data source, please see the Stackato documentation: http://docs.stackato.com/admin/cluster/external-db.html#postgresql