ats-min.com

Plex Media Server on Raspberry Pi

2018年2月24日 / atsmin / 0 Comments

Thanks to besn0847/arm-plex docker image, it’s possible to run Plex Media Server on Raspberry Pi. This docker image is using third party package.

Here is ansible task that gets docker image and runs container.

- hosts: pi
  become: true 
- tasks                                                                                                                                                    - name: Creates library directory                                                                                                                              
      file:
          path: /mnt/data/library
          state: directory

    - name: Plex media server container present
      docker_container:
          name: plex
          image: besn0847/arm-plex
          state: present
      tags:
          - plex

    - name: Restart container
      docker_container:
          name: plex
          image: besn0847/arm-plex
          state: started
          network_mode: host
          exposed_ports:
              - 32400
          volumes:
              - "/mnt/data/library:/data"
      tags:
          - plex

- hosts: pi

become: true

- tasks - name: Creates library directory

file:

path: /mnt/data/library

state: directory

- name: Plex media server container present

docker_container:

name: plex

image: besn0847/arm-plex

state: present

tags:

- plex

- name: Restart container

docker_container:

name: plex

image: besn0847/arm-plex

state: started

network_mode: host

exposed_ports:

- 32400

volumes:

- "/mnt/data/library:/data"

tags:

- plex

After running playbook, Plex Web App is available at “http://{{ raspberry IP }}:32400/web/index.html”, but at first you have to sign up Plex account. The “network-mode: host” is required, otherwise you can’t access Plex by “Authorization Error”.

NFS mount on boot(Arch Linux)

2017年10月7日 / atsmin / 0 Comments

At first, I added the following line to /etc/fstab. Then I could mount it by a command “mount -a”.

192.168.x.x:/mnt/data    /mnt/nfs    nfs    defaults    0    0

1	192.168.x.x:/mnt/data /mnt/nfs nfs defaults 0 0

However, it isn’t mounted on boot automatically. I searched google, and it might be a problem is that the system tried to mount nfs before networking up. To avoid this, there is a mount option “_netdev”.

192.168.x.x:/mnt/data    /mnt/nfs    nfs    defaults,_netdev    0    0

1	192.168.x.x:/mnt/data /mnt/nfs nfs defaults,_netdev 0 0

After adding the option though it still doesn’t mount on boot. In addition, I had to enable a systemd target named “systemd-networkd-wait-online.service”, otherwise the systemd still might try to mount the nfs before networking up.

sudo systemctl enable systemd-networkd-wait-online.service

1	sudo systemctl enable systemd-networkd-wait-online.service

Finally it turned to be mounted on boot correctly:D.

Solving NFS Mounts at Boot Time

https://wiki.archlinux.org/index.php/NFS#Automounting_shares_with_systemd-networkd

Let’s encrypt renew

2017年7月23日 / atsmin / 0 Comments

When I renew my certificate by the following command with running nginx, and error occured.

./certbot-auto renew --dry-run

Problem binding to port 443: Could not bind to IPv4 or IPv6.. Skipping.

./certbot-auto renew --dry-run

Problem binding to port 443: Could not bind to IPv4 or IPv6.. Skipping.

As the document says, adding –webroot and -w option solved the problem. 😀

./certbot-auto renew --dry-run --webroot -w /var/www/html

1	./certbot-auto renew --dry-run --webroot -w /var/www/html

fctix + mozc(Arch Linux)

2017年7月17日 / atsmin / 0 Comments

Once I installed fctix-mozc package and make ~/.xprofile following the wiki. Then I noticed I can enter Japanese inside only shell console, but can’t in other applications like firefox. The problem is that I only installed one package of fctix-im package group. It turned work fine after I installed all input method packages that the fctix-im includes(fcitx-gtk2, fcitx-gtk3, fcitx-qt4 and fcitx-qt5):D

Mastodon on Raspberry pi

2017年5月13日 / atsmin / 0 Comments

Official Mastodon github doc says that the following softwares are required to run Mastodon.

Nginx
Docker
Docker-compose

Nginx is userd as a reverse proxy. Docker can be installed by the below command written in official Raspbian doc.

curl -sSL https://get.docker.com | sh

1	curl -sSL https://get.docker.com \| sh

However, official docker-compose can’t be used because it doesn’t compatible to Raspberry pi ARM CPU.

There is a docker-compose for ARM project, arm-compose in github. Though the readme says it isn’t maintaind anymore, anyway go ahead. Installation commands are written in the readme.

Not only docker-compose, official Mastodon docker image doesn’t work in ARM CPU environment as well, but there is a docker image for ARM, rpi-mastodon . However, using this original image we can’t compile Mastodon javascript later as menthioned in this Issue. Modified Dockerfile is here.

Though we can build rpi-mastodon images by docker build command as written in documents, there is another problem. After precompile, when I access https://localhost:3000, browser says that

404 /javascripts/application.js 
404 /stylesheets/application.css

1 2	404 /javascripts/application.js 404 /stylesheets/application.css

The problem is also mentioned in this Issue. Checking inside mastodon-web container, actually these files didn’t exist.

$ docker exec -it {container id of mastodon-web} /bin/sh

# ls public/javascripts/application.js
No such file or directory

# ls public/stylesheets/application.css
No such file or directory

$ docker exec -it {container id of mastodon-web} /bin/sh

# ls public/javascripts/application.js

No such file or directory

# ls public/stylesheets/application.css

No such file or directory

The precompiled files are found in public/assets directory with different names.

# ls public/assets/application-ead9c7441f487a0fef44a4e7e1129e67ca5ad203a91762b
d6ec6f32850046b2f.js

# ls public/assets/application-b7d32e1a05cf50241f3074c5038f423a251e081f210ad7f
dc238029d85f502f2.css

# ls public/assets/application-ead9c7441f487a0fef44a4e7e1129e67ca5ad203a91762b

d6ec6f32850046b2f.js

# ls public/assets/application-b7d32e1a05cf50241f3074c5038f423a251e081f210ad7f

dc238029d85f502f2.css

After copy or symlink these files inside public/javascripts or stylesheets directory, it worked. Other application_public.js or some images are also located in public/assets directory, so copy or symlink them as well.

Ubuntu 16.04: Can’t login Desktop (infinite loop)

2017年4月26日 / atsmin / 0 Comments

One day, suddenly it turned that I couldn’t login desktop even if I enter correct password. Stackoverflow said that the reason is ~/.Xauthority permisson.

$ ls -lA ~/.Xauthority
-rw------- 1 aminami aminami 51  4月 26 21:11 .Xauthority
$ chown {user_name}:{user_name} ~/.Xauthority

$ ls -lA ~/.Xauthority

-rw------- 1 aminami aminami 51 4月 26 21:11 .Xauthority

$ chown {user_name}:{user_name} ~/.Xauthority

It solved the problem.

Ubuntu16.04: PHP7 MySQL connect

2017年1月9日 / atsmin / 0 Comments

When I tried to run Zabbix locally, the PHP frontend page didn’t show by the following error.

PHP Fatal error:  Uncaught Error: Call to undefined function mysqli_connect()

1	PHP Fatal error: Uncaught Error: Call to undefined function mysqli_connect()

After adding “php-mysql” package, it turned to work fine.

sudo apt-get install php-mysql

1	sudo apt-get install php-mysql

Linux: How to change hostname permanently in CentOS

2016年12月25日 / atsmin / 0 Comments

To change hostname permanently in CentOS, use the following hostnamectl command (not hostname).

hostnamectl set-hostname myhostname --static

1	hostnamectl set-hostname myhostname --static

Linux: Ubuntu 16.04 fcitx-mozc couldn’t be install

2016年12月4日 / atsmin / 0 Comments

After updating Ubuntu from 14.04 to 16.04, “Langauage Support” system settings didn’t work and the following error occured.

$ sudo apt-get install fcitx-mozc   
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 fcitx-mozc : Depends: mozc-server (= 2.17.2116.102+gitfd0f5b34+dfsg-1ubuntu1.1) but 1:1.5.1053.102-1~ppa4 is to be installed
              Recommends: mozc-utils-gui (= 2.17.2116.102+gitfd0f5b34+dfsg-1ubuntu1.1) but 1:1.5.1053.102-1~ppa4 is to be installed

$ sudo apt-get install fcitx-mozc

Reading package lists... Done

Building dependency tree

Reading state information... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:

The following packages have unmet dependencies:

fcitx-mozc : Depends: mozc-server (= 2.17.2116.102+gitfd0f5b34+dfsg-1ubuntu1.1) but 1:1.5.1053.102-1~ppa4 is to be installed

Recommends: mozc-utils-gui (= 2.17.2116.102+gitfd0f5b34+dfsg-1ubuntu1.1) but 1:1.5.1053.102-1~ppa4 is to be installed

When I purged mozc-server package, it turned to work fine.

sudo apt-get purge mozc-server

1	sudo apt-get purge mozc-server

PostgreSQL: could not connect to server

2016年11月25日 / atsmin / 0 Comments

When I started PostgreSQL server with specific database cluster on Ubuntu 14.04, the client coundn’t connect to the server.

# start server
postgres@ubuntu:~$ pg_ctl -D /usr/local/pgsql/data -l logfile start
# connect to the server
postgres@ubuntu:~$ psql
psql: could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

# start server

postgres@ubuntu:~$ pg_ctl -D /usr/local/pgsql/data -l logfile start

# connect to the server

postgres@ubuntu:~$ psql

psql: could not connect to server: No such file or directory

Is the server running locally and accepting

connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

After I changed ‘unix_socket_directories’ in the postgresql.conf, it worked.

#unix_socket_directories = '/var/run/postgresql'        # comma-separated list of directories
unix_socket_directories = '/tmp'        # comma-separated list of directories

1 2	#unix_socket_directories = '/var/run/postgresql' # comma-separated list of directories unix_socket_directories = '/tmp' # comma-separated list of directories

Just another programmer's site