Author: Alejandro Aguilar Sierra | Contact: [email protected]

Laboratorio Nacional de Observación de la Tierra, UNAM, México

Hi GEONETCasters! This procedure was kindly written by Alejandro Aguilar Sierro, from LANOT (National Laboratory for Earth Observation) at UNAM (National Autonomous University of Mexico).

Please check the other contributions from the LANOT team at the following links:

• Products generated by the comunity: LANOT (Part I)
• Products generated by the comunity: LANOT (Part II)

Thanks LANOT! And below, the procedure written by Alejandro Sierra:

In this blog post we’ll learn how to install the GNC-A ingestion software (KENCAST FAZZT PROFESSIONAL CLIENT VERSION 9.2) on Debian 10.3.

First, some important notes:

• This procedure was tested on Linux Debian 10.x, which is the current stable version. If your system has a previous version, the update is advised.
• FAZZT v 9.2 currently doesn’t support Debian by default, and the procedure described here is different to the one used to install on Ubuntu, so if you still want to do it, do it at your own risk. You had been warned.
• In order to install FAZZT, is necessary to install Apache2 and the PostgreSQL Database, as shown on this procedure.
• It is mandatory to create an account called “fazzt”. This is required for the FAZZT database to work.

Why Debian?

• It is a very robust distribution with 25 years of experience, completely able to be used in servers.
• Usually it is updated faster than other distributions and have a wider base of packages and software.
• It’s not as friendly as Ubuntu but as efficient as CentOs.

PART I: PREINSTALL

Install Apache2 and PostgreSQL, as root:

# apt update
# apt install apache2 postgresql

Create the user fazzt:

# adduser fazzt

Get the most recent installation file for CentOs from KenCast. In our case, we will use the following installer, provided by KenCast:

Fazzt-Professional-Client-rhel7-9.2.0.0-1.x86_64.rpm

Now, the most important part of the trick: use the Debian tool called alien to create a corresponding “deb” file.

If that is too complicated, by all means you can get ours from the following link:

fazzt-professional-client-rhel7_9.2.0.0-2_amd64.deb

PART II: INSTALLATION

Use the generated “deb” file to install the Fazzt Professional Client:

# dpkg -i fazzt-professional-client-rhel7_9.2.0.0-2_amd64.deb

Now, the “alien” tool did a very good but imperfect work, so you will have to do a couple of adjustments by hand. The Apache’s configuration and module files were installed in the wrong directory. Just copy them to the correct one:

# cp -p /etc/httpd/conf.d/S10-fsp.conf /etc/apache2/conf-available/S10-fsp.conf
# cp -p /etc/httpd/conf.d/S60-fazzt-admin.conf /etc/apache2/conf-available/S60-fazzt-admin.conf
# cp -p /etc/httpd/modules/mod_fsp.so /usr/lib/apache2/modules/mod_fsp.so

Create the file /etc/apache2/mods-available/fsp.load with the following line:

LoadModule fsp_module /usr/lib/apache2/modules/mod_fsp.so

Enable the config files and module:

# a2enconf S10-fsp
# a2enconf S60-fazzt-admin
# a2enmod fsp

Correct a couple of mistakes in these files:

/etc/apache2/conf-available/S10-fsp.conf
-LoadModule fsp_module modules/mod_fsp.so
+#LoadModule fsp_module modules/mod_fsp.so

and:

/etc/apache2/conf-available/S60-fazzt-admin.conf
-		ErrorLog logs/Fazzt-admin-error.log
-		CustomLog logs/Fazzt-admin-access.log common
+		ErrorLog Fazzt-admin-error.log
+		CustomLog Fazzt-admin-access.log common

Don’t forget to install the FAZZT KenCast license provided by KenCast:

# /usr/share/Fazzt/bin/fconf set license PCXXXXXX.kcl

Now you are ready. Start the FAZZT service:

# systemctl start fazzt.service

If everything was right, you must see your service active and without errors. The first start will create the database and its corresponding user and password, and the same for fazzt, which you can verify from the user postgres.

# su - postgres
$ psql fazzt
psql (11.7 (Debian 11.7-2.pgdg100+1))
Type "help" for help.

fazzt=# \dt
List of relations
Schema |               Name               | Type  | Owner
--------+----------------------------------+-------+-------
public | applicationinstances             | table | fazzt
public | applicationschedules             | table | fazzt
public | applicationservices              | table | fazzt
public | applicationservicetypes          | table | fazzt
public | applicationtypes                 | table | fazzt
public | channels                         | table | fazzt
public | channeltypes                     | table | fazzt
public | defaultschedule                  | table | fazzt
public | fazzttbls                        | table | fazzt
public | forwardingconditionactiondefault | table | fazzt
public | forwardingconditionactionrules   | table | fazzt
public | forwardingrules                  | table | fazzt
public | globalattributes                 | table | fazzt
public | notes                            | table | fazzt
public | receivedfiles                    | table | fazzt
public | schedule                         | table | fazzt
public | selectivereception               | table | fazzt
public | selectivereceptiongroups         | table | fazzt
public | streams                          | table | fazzt
public | transmissions                    | table | fazzt
(20 rows)

fazzt=#

If you don’t see those tables, something went wrong. Perhaps you just have to comment the line 382 of the startup file /usr/share/Fazzt/bin/fazzt-setup since createlang is no more supported nor necessary in current Postgres. Try again.

It is important to note that Debian uses nftables instead of iptables to configure a firewall and you will have to open the port 4039 and accept everything from the interface you use to connect the decoder. In my case, I had to add these lines to /etc/nftables.conf and restart the nftables service.

iifname eno4 accept
tcp dport 4039 accept

Now restart Apache.

# systemctl restart apache2

PART III: KENCAST FAZZT CONFIGURATION

Let’s configure the FAZZT Client for the GNC-A ingestion. At the menu on the left, choose “Configuration” -> “Channels” and then, at the “Channels” window, choose “Channels Defaults”. At “Interface”, choose the IP address of the Network Card where you have your DVB-S receiver connected. Click on “Save”.

– Select the ingestion folder at “Configurations” – “Storage Settings” – “Virtual Paths: View/Edit”

– Click at the backslash “\” as shown on the image below and choose the folder where the received files will be stored. In this procedure we suggested “/data/fazzt” but it may be any folder you want.

– Back to the “Channels” interface, click at the “1.Main” channel:

– And at “Interface”, choose “default”:

– After a while (a couple of minutes), you should see the GNC-A Broadcast channels being listed at the “Configuration” – “Channels” interface.

Congreatulations! Your GNC-A station is ingesting!

To check other procedures to install the FAZZT PROFESSIONAL CLIENT, please access the links below:

• Installing the GNC-A Ingestion software on CentOS 6.9: The Hard Way
• Installing the GNC-A Ingestion software on CentOS 6.9: The Easy Way
• Installing the GNC-A Ingestion software on Ubuntu 16.04: The Hard Way
• Installing the GNC-A Ingestion software on Ubuntu 16.04: The Easy Way

Hi GEONETCasters,

In order to reset the FAZZT database on Linux (thus liberating lots of space on the Hard Drive), please follow the procedure below:

1-) As root, stop the FAZZT service:

service fazzt stop

2-) Start the postgresql service:

# service postgresql-9.4 start

3-) Remove your “fazzt” database and your “fazzt” user:

# su - postgres
# dropdb fazzt
# dropuser fazzt

4-) Quit the database:

$ exit

5-) Stop the postgresql service:

# service postgresql-9.4 stop

6-) Remove your postgresql data folder:

# rm -rf /var/lib/pgsql/9.4/data/

7-) Reconfigure your database with the procedure below:

– Configure the database for the initialization:

# service postgresql-9.4 initdb

–  Start the database:

# service postgresql-9.4 start

– Configure the database to start automatically:

# chkconfig postgresql-9.4 on
# chkconfig --level 345 postgresql-9.4 on

– Restart the database:

# service postgresql-9.4 restart

– Edit the file “postgresql.conf” file found at /var/lib/pgsql/9.4/data:

# gedit /var/lib/pgsql/9.4/data/postgresql.conf

…Changing the following line on session “CONNECTIONS AND AUTENTICATION” (line 54 more or less):

listen_addresses = '*' #What IP address (es) to listen on;

– At the same session, four lines below, remove the comments “#”, if they exist:

port 5432
max_connections = 100

– In the same file, further down, in the ** AUTOVACUUM PARAMETERS ** session (line 463 more os less), remove the comment “#”, and change it to “off”

autovacuum = off # Enable autovacuum subprocess? 'on'

– Save and close the “postgresql.conf” file.

– Edit the “pg_hba.conf” file found at gedit /var/lib/pgsql/9.4/data/

# gedit /var/lib/pgsql/9.4/data/pg_hba.conf

 …Changing the following lines at the end of the file from peer or ident to “trust”:

# TYPE DATABASE USER ADDRESS METHOD
# "local" is for Unix domain socket connections only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     postgres                                peer
#host    replication     postgres        127.0.0.1/32            ident
#host    replication     postgres        ::1/128                 ident

– Also, add the following line in the end of the same session:

# host all all 0.0.0.0/0 trust

– This is what you should have

# TYPE DATABASE USER ADDRESS METHOD
# "local" is for Unix domain socket connections only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     postgres                                peer
#host    replication     postgres        127.0.0.1/32            ident
#host    replication     postgres        ::1/128                 ident
host all all 0.0.0.0/0 trust

– Save and close the “pg_hba.conf” file.

 – Change the memory limit used by the database, editing the “limits.conf” file found at gedit /etc/security/

# gedit /etc/security/limits.conf

 …Adding the following lines before the “End of file”

fazzt soft nofile 4096
fazzt hard nofile 4096
# End of file

– Restart the PostgreSQL:

# service postgresql-9.4 restart

– Enter the PostgreSQL:

su - postgres

– Create the “fazzt” database:

$ createdb fazzt
$ createuser -s -d -r -l -P fazzt

– You will be asked for inserting a new password for the database. It may be the same as the root. However, you may use any password you want. Insert the chosen password twice (e.g.: fazzt and fazzt).

Enter password for new role: fazzt
Enter it again: fazzt

 – Quit the Postgresql:

$ exit

 – Restart Postgresql:

# service postgresql-9.4 restart

 – Return to the database and verify the created account:

# su - postgres
$ psql -h localhost -U fazzt fazzt

– The output of the previous command should be:

Type “help” for help
fazzt=#

 – Quit the Database with the “\q” command:

postgres=# \q
$ exit

Your FAZZT Database was successfully reset!

5-) RESET your FAZZT Client:

# service fazzt reset

6-) Reconfigure your FAZZT Client according to the procedure below. Wait for the channels to reappear.

KENCAST FAZZT CONFIGURATION

 – Let’s configure the FAZZT Client for the GNC-A ingestion. The configuration is the same for versions 8.1 or 9.0. At the menu on the left, choose “Configuration” -> “Channels” and then, at the “Channels” window, choose “Channels Defaults”. At “Interface”, choose the IP address of the Network Card where you have your DVB-S receiver connected. Click on “Save”.

– Select the ingestion folder at “Configurations” – “Storage Settings” – “Virtual Paths: View/Edit”

– Click at the backslash “\” as shown on the image below and choose the folder where the received files will be stored. In this procedure we suggested “/data/fazzt” but it may be any folder you want.

– Back to the “Channels” interface, click at the “1.Main” channel:

– And at “Interface”, choose “default”:

– After a while (a couple of minutes), you should see the GNC-A Broadcast channels being listed at the “Configuration” – “Channels” interface.