Alpine Linux - User contributions [en]

Zabbix - cgi and mysql

2019-01-24T16:25:58Z

Rhencke: Fix dash

The purpose of this document is to assist in installing the Zabbix server software and Zabbix agent on the Alpine Linux operating system. Instructions on how to configure and use Zabbix - as well as many useful tutorials - can be found at http://www.zabbix.com.

{{Note|The minimum required version of Alpine Linux required to install Zabbix is Alpine 2.2. this guide has been updated to zabbix 3.0}}

= Install Lighttpd, and PHP =

{{:Setting Up Lighttpd With FastCGI}}

= Configure PostgreSQL =

Install PostgreSQL

{{Cmd|apk add postgresql postgresql-client}}

Now configure PostgreSQL:
{{Cmd|/etc/init.d/postgresql setup
/etc/init.d/postgresql start
rc-update add postgresql}}

= Install Zabbix =

{{Cmd|apk add zabbix zabbix-pgsql zabbix-webif zabbix-setup}}

Now we need to set up the zabbix database. Substitute '*********' in the example below for a real password:

{{Cmd|<nowiki>psql -U postgres
postgres=# create user zabbix with password '*********';
postgres=# create database zabbix owner zabbix;
postgres=# \q
cd /usr/share/zabbix/database/postgresql
cat schema.sql | psql -U zabbix zabbix
cat images.sql | psql -U zabbix zabbix
cat data.sql | psql -U zabbix zabbix</nowiki>}}

Create a softlink for the Zabbix web-frontend files:

{{Cmd|rm /var/www/localhost/htdocs -R
ln -s /usr/share/webapps/zabbix /var/www/localhost/htdocs}}

Edit PHP configuration to satisfy some zabbix requirements. Edit /etc/php/php.ini and configure the following values at least:

<pre>
Max_execution_time = 600
Expose_php = off
Date.timezone = <insert your timezone here>
post_max_size = 32M
upload_max_filesize = 16M
max_input_time = 600
memory_limit = 256M
</pre>

Configure the following entries in /etc/zabbix/zabbix_server.conf, where DBPassword is the password chosen for the database above:

<pre>
DBName=zabbix

# Database user

DBUser=zabbix

# Database password
# Comment this line if no password used

DBPassword=*********

FpingLocation=/usr/sbin/fping
</pre>

Start Zabbix server:

{{Cmd|rc-update add zabbix-server
/etc/init.d/zabbix-server start}}

Fix permissions on conf directory.

{{Cmd|chown -R lighttpd /usr/share/webapps/zabbix/conf}}

You should now be able to browse to the Zabbix frontend: http://yourservername/.

or

You should now be able to browse to the Zabbix setup frontend: http://yourserverip/instal.php.

Follow the setup instructions to configure Zabbix, supplying the database information used above.

After setup, login using: Login name: '''Admin''' Password:'''zabbix'''. (as described at http://www.zabbix.com/documentation/1.8/manual/installation)

Finally, Zabbix requires special permissions to use the fping binary.

{{Cmd|chmod u+s /usr/sbin/fping}}

= Install Zabbix Agent on Monitored Servers =

Zabbix can monitor almost any operating system, including Alpine Linux hosts. Complete the following steps to install the Zabbix agent on Alpine Linux.

{{Note|Support to allow zabbix-agentd to view running processes on Alpine Linux has been added since linux-grsec-2.6.35.9-r2. Please ensure you have that kernel installed prior to attempting to run zabbix-agentd.}}

Ensure that the readproc group exists (support added since alpine-baselayout-2.0_rc1-r1), by adding the following line to /etc/group:

{{Cmd|readproc:x:30:zabbix}}

Install the agent package:

{{Cmd|apk add zabbix-agent}}

Edit the /etc/zabbix/zabbix_agentd.conf file and configure at least the following option:
<pre>
Server=<ip or hostname of zabbix server>
Hostname=<ip or hostname of zabbix agent>
ListenPort=10050
</pre>

Start the zabbix-agent:

{{Cmd|rc-update add zabbix-agentd
/etc/init.d/zabbix-agentd start}}

In case you want to monitor using SNMP agent on remote machines you have to add these packages on zabbix server:

{{Cmd|apk add net-snmp net-snmp-tools}}

And add these packages on remote machines:

{{Cmd|apk add net-snmp }}

= Optional: Crash course in adding hosts, checks, and notifications =

''Note:'' This is optional since it's not specific to Alpine Linux, but I wanted a couple notes for how to perform a simple check on a server that doesn't have the agent installed on it, and be notified on state changes.

Administration -> Media Types -> Email
* Setup server, helo, email from address

Administration -> Users
* Setup each user who'll get notified, make sure they have media type "Email" added with their address

Configuration -> Hosts -> Create host
* In Linux Servers hostgroup
* Define dns name, ip, connect by IP
* If the machine is a simple networking device that will only be monitored using SNMP, add it to Template_SNMPv2_Device, and you're done.

Configuration -> Templates -> Create template
* Give it a name (Template_Alpine_Linux_Infra_HTTP)
* In Templates group

Configuration -> Templates -> Template_Alpine_Linux_Infra_HTTP -> Items
* Create Item
* Host: Template_Alpine_Linux_Infra_HTTP
* Description: HTTP Basic Check
* Type: Simple_check
* Key: http,80

Configuration -> Templates -> Template_Alpine_Linux_Infra_HTTP -> Triggers
* Create Trigger
* Name: "HTTP Trigger"
* Expression: {Template_Alpine_Linux_Infra_HTTP:http,80.last(0)}#1
* Severity: High

Configuration -> Actions ->
* Create Action
* name: Email notifications
* Event source: triggers
* Default Subject: add "{HOST.DNS}:" to the beginning
* Default message: add "{HOST.DNS}:" to the beginning
* Conditions: make host have to be from "Linux Servers" hostgroup, and Template_Alpine_Linux_Infra_HTTP:HTTP trigger" is not 1
* Email affected users

[[Category:Monitoring]]
[[Category:PHP]]
[[Category:SQL]]

Wi-Fi

2016-06-19T15:53:12Z

Rhencke: Undo revision 12864 by Rhencke (talk) - ugh, I was wrong

This document describes how to set up a wireless network connection with WPA encryption.

First make sure your wireless drivers are loded properly. (if you are using a Broadcom chipset, see note at the end of this post.)

Install {{Pkg|wireless-tools}} and {{Pkg|wpa_supplicant}}.
{{Cmd|apk add wireless-tools wpa_supplicant}}

Bring the link up so we can look for wireless networks. (An error here means you probably need extra drivers/firmware.)
{{Cmd|ip link set wlan0 up}}

Find a network to connect to. Look for the ESSID. In this example we will use the ESSID "MyNet".
{{Cmd|iwlist wlan0 scanning}}

Lets set the ESSID:
{{Cmd|iwconfig wlan0 essid MyNet}}

We need to create a shared key for wpa_supplicant.
{{Cmd|wpa_passphrase MyNet > wpa.conf}}
It will wait for the password from stdin. Enter the password and enter. Now you will have a {{Path|wpa.conf}} file with the preshared key.

Start wpa_supplicant with the generated config:
{{Cmd|wpa_supplicant -Dwext -iwlan0 -c ./wpa.conf}}

From another console, start dhcpcd:
{{Cmd|udhcpc -i wlan0}}

You should get an IP address.

You then want to make the connection process automatic on boot-up. Open {{Path|/etc/network/interfaces}} and add the following stanza:
auto wlan0
iface wlan0 inet dhcp

You will also need to set wpa_supplicant to start automatically on boot:
{{Cmd|rc-update add wpa_supplicant boot}}

Next, create {{Path|/etc/wpa_supplicant/}} (permissions of 755 with root:root are fine), and move {{Path|wpa.conf}} into that folder, renaming it to {{Path|wpa_supplicant.conf}}.

Reboot and check that you are associated with the access point:
{{Cmd|iwconfig wlan0}}
and check that you got a DHCP lease:
{{Cmd|ifconfig wlan0 {{!}} grep addr}}

{{Note|BROADCOM WIFI CHIPSET USERS will need to compile the firmware manually for their chipset. First, apk add alpine-sdk, then git clone aports from git.alpinelinux.org, switch to the aports/non-free/b43-firmware folder, then run abuild -r. Install the generated apk file. Run fwcutter, and you should be good to go.}}

[[Category:Networking]]

Wi-Fi

2016-06-19T07:20:58Z

Rhencke: Instructions did not work unless udhcpd was added.

This document describes how to set up a wireless network connection with WPA encryption.

First make sure your wireless drivers are loded properly. (if you are using a Broadcom chipset, see note at the end of this post.)

Install {{Pkg|wireless-tools}} and {{Pkg|wpa_supplicant}}.
{{Cmd|apk add wireless-tools wpa_supplicant}}

Bring the link up so we can look for wireless networks. (An error here means you probably need extra drivers/firmware.)
{{Cmd|ip link set wlan0 up}}

Find a network to connect to. Look for the ESSID. In this example we will use the ESSID "MyNet".
{{Cmd|iwlist wlan0 scanning}}

Lets set the ESSID:
{{Cmd|iwconfig wlan0 essid MyNet}}

We need to create a shared key for wpa_supplicant.
{{Cmd|wpa_passphrase MyNet > wpa.conf}}
It will wait for the password from stdin. Enter the password and enter. Now you will have a {{Path|wpa.conf}} file with the preshared key.

Start wpa_supplicant with the generated config:
{{Cmd|wpa_supplicant -Dwext -iwlan0 -c ./wpa.conf}}

From another console, start dhcpcd:
{{Cmd|udhcpc -i wlan0}}

You should get an IP address.

You then want to make the connection process automatic on boot-up. Open {{Path|/etc/network/interfaces}} and add the following stanza:
auto wlan0
iface wlan0 inet dhcp

You will also need to set wpa_supplicant and udhcpd to start automatically on boot:
{{Cmd|rc-update add wpa_supplicant boot
rc-update add udhcpd boot
}}

Next, create {{Path|/etc/wpa_supplicant/}} (permissions of 755 with root:root are fine), and move {{Path|wpa.conf}} into that folder, renaming it to {{Path|wpa_supplicant.conf}}.

Reboot and check that you are associated with the access point:
{{Cmd|iwconfig wlan0}}
and check that you got a DHCP lease:
{{Cmd|ifconfig wlan0 {{!}} grep addr}}

{{Note|BROADCOM WIFI CHIPSET USERS will need to compile the firmware manually for their chipset. First, apk add alpine-sdk, then git clone aports from git.alpinelinux.org, switch to the aports/non-free/b43-firmware folder, then run abuild -r. Install the generated apk file. Run fwcutter, and you should be good to go.}}

[[Category:Networking]]