Skip to content

Page Header

Posts categoriezed as IT

Run Apache on Windows as Reverse Proxy for Tomcat

Run Apache on Windows as Reverse Proxy for Tomcat published on

Steps

  1. Make sure, in %TOMCATHOME%\conf\server.xml the connector is running on 8080 for http and 8443 for https, and the default 8009 on AJP
  2. Download Apache from http://www.apachelounge.com/download/ or use the ZIP from the screenFOOD server deployment artifcats
  3. Install "C++ Redistributable Visual Studio 2017" provided in the deployment artifacts "VC_redist.x64.exe"
  4. Unzip Apache to c:\opt\Apache24
  5. Copy httpd.conf and reverseproxy.conf to C:\opt\Apache24\conf. Make sure, Include conf/reverseproxy.conf is set properly in httpd.conf
  6. make sure in httpd.conf the SRVROOT is correct according to the install folder 
      Define SRVROOT "C:/opt/Apache24/
  7. Open CMD and CD to C:\opt\Apache24\bin and run httpd.exe.
    • if it starts, install the service with 
      httpd.exe -k install

    • if it does not start, some usefull errors are printed. Perhaps you have to activate/deactivate some module

  8. Go to services.msc and start "Apache2"

find by date and tar them

find by date and tar them published on No Comments on find by date and tar them

If you have a big log folder and you want to tar the newest log files in to one tar.gz file, then you can use the following:

find /opt/tomcat/logs/ -type f -newermt 2013-06-09 | tar cvzf testfind.tar.gz -T - --null

I do not know the meaning of -T - --null, but it works.

 

Perhaps your find version is to old for the newermt statement. With find version 4.2.27 it did not work. Then you could use -mtime, for modification time.
mtime is the number * 24 h, do find all files older newer then one day, you can use:

find /opt/tomcat/logs/ -type f -mtime 1

+1 would mean older than one day

Upgrade PostgreSQL Database from 9.4 to 9.6 on openSUSE

Upgrade PostgreSQL Database from 9.4 to 9.6 on openSUSE published on No Comments on Upgrade PostgreSQL Database from 9.4 to 9.6 on openSUSE

This tutorial shows how to upgrade PostgreSQL from 9.4 (openSUSE 42.2) to 9.6 (openSUSE 42.3)

  1. Stop postgresql and disable service 
    systemctl stop postgresql.service
systemctl disable postgresql.service
  2. Install PostgreSQL 9.6 (9.4 should still be installed after the update) 
    zypper -n install postgresql96 postgresql96-server postgresql96-contrib
  3. Move current cluster and create new data dir with user postgres 
    mv /var/lib/pgsql/data/ /var/lib/pgsql/data94/
su postgres -c "mkdir /var/lib/pgsql/data"
  4. Enable service, start it to create new database cluster at data folder, and stop service again to prepare the following upgrade 
    systemctl enable postgresql.service
systemctl start postgresql.service
systemctl stop postgresql.service
  5. Run pg_upgrade where -b is old bin dir, -B is new bin dir, -d is old data dir, and -D new data dir. This must run as user postgres ( su - postgres ) 
    su - postgres -c "pg_upgrade -b /usr/lib/postgresql94/bin/ -B /usr/lib/postgresql96/bin/ -d /var/lib/pgsql/data94/ -D /var/lib/pgsql/data"
  6. Copy the pg_hba.conf from old data dir to the new one (if you changed something at postgresql.conf you could copy that to the new data folder too). After that, start the postgresql service. 
    cp /var/lib/pgsql/data94/pg_hba.conf /var/lib/pgsql/data
systemctl start postgresql.service
  7. Try to login to postgresql, Version 9.6.x should be printed, leave with \q 
     # psql -U postgres
psql (9.6.4)
Type "help" for help.

postgres=# \q
  8. If you don't need the old cluster data, run this: 
    /var/lib/pgsql/delete_old_cluster.sh

allow access to postgresql from outside

allow access to postgresql from outside published on No Comments on allow access to postgresql from outside

With this steps you can configure PostgreSQL to accept connections from the LAN on Port 5432.

  1. edit /var/lib/pgsql/data/postgresql.conf
    listen_addresses = '*'
  2. edit /var/lib/pgsql/data/pg_hba.conf add the network you want to allow like: host all all 192.168.190.0/24 md5
    The file looks then like:

    # "local" is for Unix domain socket connections only
local   all             all                                     trust
# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
host    all             all             192.168.190.0/24        md5
# IPv6 local connections:
host    all             all             ::1/128                 md5
  3. reload postgresql
    systemctl restart postgresql.service
  4. check connection with pgAdmin or an other tool

Syntax Highlighting for NGINGX on Vim

Syntax Highlighting for NGINGX on Vim published on No Comments on Syntax Highlighting for NGINGX on Vim

nginx.conf for Vim

https://gist.github.com/2called-chaos/5073996

#!/bin/sh
mkdir -p ~/.vim/syntax/
cd ~/.vim/syntax/
wget http://www.vim.org/scripts/download_script.php?src_id=19394
mv download_script.php\?src_id\=19394 nginx.vim
cat > ~/.vim/filetype.vim << EOF
au BufRead,BufNewFile /etc/nginx/*,/usr/local/nginx/conf/* if &ft == '' | setfiletype nginx | endif
EOF
Categories

Page Footer