jeffcosta.comJeff Acosta

Skip to content My musings on technology Scroll down to content Posts Posted on September 4, 2017 September 4, 2017 Disable Thumbd Daemon on Synology DiskStation I have no need for the FileStation app to generate thumbnails of the content I store on my Synology Diskstation NAS, but when I looked at what was running, it spun up several daemons anyway: 6790 ? Ssl 0:00 /var/packages/FileStation/target/sbin/thumbd 6792 ? Ss 0:00 /var/packages/FileStation/target/sbin/thumbd 6793 ? Ss 0:00 /var/packages/FileStation/target/sbin/thumbd 6818 ? Ssl 0:13 /var/packages/CloudSync/target/sbin/syno-cloud-syncd /volume1/@cloudsync/config/daemon.conf 6987 ? Ss 0:00 /var/packages/FileStation/target/sbin/thumbd 6988 ? Ss 0:00 /var/packages/FileStation/target/sbin/thumbd 6989 ? Ss 0:00 /var/packages/FileStation/target/sbin/thumbd 6990 ? Ss 0:00 /var/packages/FileStation/target/sbin/thumbd 6991 ? Ss 0:00 /var/packages/FileStation/target/sbin/thumbd 6992 ? Ss 0:00 /var/packages/FileStation/target/sbin/thumbd 6993 ? Ss 0:00 /var/packages/FileStation/target/sbin/thumbd 6994 ? Ss 0:00 /var/packages/FileStation/target/sbin/thumbd You cannot disable or turn off the FileStation functionality without breaking some core GUI items that are required for normal functioning in the web interface. But, you can stop the thumbd service from running and chewing up unnecessary system resources. Here’s how: Browse to the /var/packages/FileStation/target/etc/conf directory. Issue this command to rename the thumbd.conf file: mv thumbd.conf thumbd.conf.orig Reboot the Synology device. SSH into the device and you should no longer see any instance of the thumbd Posted on March 31, 2016 Disabling Indexing On the Synology DS216+ After 6 years, I finally upgraded my Synology DS209 to a DS216j, and still find indexing to be a problem service that I want to turn off. A few things I found out about how the indexing service is setup on the newer DS216j: 1) Finding the running index processes: ps ax|grep index 6291 ? SNs 0:00 /usr/syno/sbin/synoindexd 6788 ? SN 0:00 /usr/syno/sbin/synoindexscand 6789 ? SN 0:00 /usr/syno/sbin/synoindexworkerd 6790 ? SN 0:00 /usr/syno/sbin/synoindexplugind 22715 pts/3 S+ 0:00 grep –color=auto index 2) Indexing is controlled through an Upstart job located at /usr/syno/sbin/synoindexd You can review all Upstart jobs by issuing the command “initctl list” 3) If you want to look at the index job specifically, issue the “initctl show-config synoindexd” command to reveal the specifics of the job: synoindexd start on started pgsql-adapter stop on stopping pgsql-adapter 4) If you want to review the script itself, open the /etc/init/synoindexd.conf file: description “configure network device” author “Web Application Team” start on started pgsql-adapter stop on stopping pgsql-adapter expect fork respawn respawn limit 5 10 pre-start script # make sure pgsql is running if /usr/syno/sbin/synoservice –is-enabled pgsql > /dev/null 2>&1; then echo “PGSQL service is disabled. Skip…” stop exit 1 fi end script exec /usr/syno/sbin/synoindexd post-stop script echo “Stopping Synology Index Daemon…” killall synoindexscand > /dev/null 2>&1 || true killall synoindexworkerd > /dev/null 2>&1 || true killall synoindexplugind > /dev/null 2>&1 || true killall synomediaparserd > /dev/null 2>&1 || true end script Notice that the index script is tied to the Postgresql database start. If you try killing the index service with a “kill -9” command it will kill the process, and then restart it. I have not yet tried, but perhaps the best way to stop the index service is to edit the /etc/init/synoindexd.conf file and change the “start on started pgsql-adapter” line to “stop on started pgsql-adapter.” I will update this post as I try this solution. Posted on January 17, 2016 Installing WS02 API Manager On Ubuntu Linux 14.04 There are official instructions to installing WSO2 API Manager that can be found here , but I found them lacking in critical details. The walkthrough below lays out the detailed steps for doing this. I spun up the cheapest $5/month VM at Digital Ocean to keep costs down as I experimented. These VMs have 20GB of hard disk and 512MB of RAM, which are FAR below the recommended sizing for API Manager. I recommend adhering to those guidelines if you are deploying to production. Login to Digital Ocean and spin up a preconfigured Ubuntu 14.4 x64 Droplet. Once provisioned, update the Droplet to have the latest packages (sudo apt-get update, sudo-apt-get upgrade,sudo apt-get dist upgrade) and reboot into the latest Linux kernel. I like to install HTOP for a more visual understanding of how a server is consuming resources: sudo apt-get install htop Install Oracle Java 7 (NOT a newer version – the official documents explicitly state this) ( UPDATE : the latest API Manager 1.10 fully supports JDK 1.8) sudo apt-get install python-software-properties sudo add-apt-repository ppa:webupd8team/java sudo apt-get install oracle-java7-installer Check that Java was installed properly with the “java -version” command: java version “1.7.0_80” Java(TM) SE Runtime Environment (build 1.7.0_80-b15) Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode) sudo apt-get clean all Create a 2GB swapfile to ensure you can start WSO2 in a memory-constrained environment: Create a swapfile: sudo swapoff /swapfile sudo dd if=/dev/zero of=/swapfile bs=1024 count=1024 sudo dd if=/dev/zero of=/swapfile bs=2048 count=2048 sudo mkswap /swapfile sudo swapon /swapfile sudo chown root:root /swapfile sudo chmod 0600 /swapfile sudo nano /etc/fstab /swapfile none swap sw 0 0 Edit the /etc/environment file to point two variables to their proper places: Add the following: JAVA_HOME=”/usr/lib/jvm/java-7-oracle/” CARBON_HOME=”/usr/local/opt/wso2am-1.10.0″ source /etc/environment Test the variables: echo #JAVA_HOME WSO2 needs a backing MYSQL server to run. Here is how you install it: sudo apt-get install mysql-server Set a password: mysqladmin -u root password (password) Change the max_connections variable from 100 to 2 in /etc/mysql/my.conf max_connections = 2 Import the WSO2 database schema in MySQL: mysql -u root -p WSO2AM_STATS_DB < /usr/local/opt/wso2am-1.10.0/dbscripts/stat/sql/mysql.sql Download the WS02 zipped binary from here, and copy it to the Droplet. Its 381Mb in size, so it may take awhile to download. Once the file is on the server, unzip it to the /usr/local/opt directory: mkdir -p /usr/local/opt cp wso2am-1.10.0.zip /usr/local/opt unzip wso2am-1.10.0.zip Note that logs for the server are kept in the /usr/local/opt/wso2am-1.10.0/repository/logs directory if you need to review them. The wso2carbon.log contains a great deal of useful information. Edit the server startup script (wso2server.sh), adding the same variables you added to /etc/environment to the top of the file: sudo nano /usr/local/opt/wso2am-1.10.0/bin/wso2server.sh JAVA_HOME=”/usr/lib/jvm/java-7-oracle/” CARBON_HOME=”/usr/local/opt/wso2am-1.10.0″ Edit the server startup script (wso2server.sh) to alter the JVM size parameters: sudo nano /usr/local/opt/wso2das-3.0.0/bin/wso2server.sh Scroll down to approximately line 294 Change the parameters to read: -Xms256m -Xmx1024m -XX:MaxPermSize=256m \ Start the server: /usr/local/opt/wso2am-1.10.0/bin/wso2server.sh start Note that it takes AWHILE to startup the server, as a number of applications have to be deployed. Be patient and expect high CPU usage. You can tail the wso2carbon.log file to watch startup happen: tail -f /usr/local/opt/wso2am-1.10.0/repository/logs/wso2carbon.log Stopping the server is done via the same command: /usr/local/opt/wso2am-1.10.0/bin/wso2server.sh stop If everything started successfully, you will see the assertions below in the wso2carbon.log TID: [-1234] [] [2016-01-10 20:17:11,502] INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} – Server : WSO2 API Manager-1.10.0 {org.wso2.carbon.core.internal.StartupFinalizerServic...