Problema para instalar ou atualizar plugins WordPress

Solved thanks to someone on Google+🙂

Your web host has forgotten to set up a tmp directory or to make it writable for you. If you forward the same error messages to them and mention the tmp directory they should resolve it for you.

The alternative is to override the default tmp directory by adding this line to you wp-config:

define( ‘WP_TEMP_DIR’, ABSPATH . ‘wp-content/tmp/’) ;

Then create that tmp folder in your wp-content directory and set permissions to 755. Really, though, it should be up to your host to correct.

https://wordpress.org/support/topic/moved-server-now-cant-install-or-update-plugins

Case sensitive passwords (and auditing) are a default feature of newly created Oracle 11g databases

Original: http://www.oracle-base.com/articles/11g/case-sensitive-passwords-11gr1.php

Case sensitive passwords (and auditing) are a default feature of newly created Oracle 11g databases. The Database Configuration Assistant (DBCA) allows you to revert these settings back to the pre-11g functionality during database creation. The SEC_CASE_SENSITIVE_LOGON initialization parameter gives control over case sensitive passwords. If existing applications struggle to authenticate against 11g, you can use the ALTER SYSTEM command to turn off this functionality.

SQL> SHOW PARAMETER SEC_CASE_SENSITIVE_LOGON

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
sec_case_sensitive_logon             boolean     TRUE
SQL> 

SQL> ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = FALSE;

System altered.

SQL>

The following code demonstrates the case sensitive password functionality. First, it resets the SEC_CASE_SENSITIVE_LOGON initialization parameter to TRUE and creates a new user with a mixed case password.

CONN / AS SYSDBA
ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = TRUE;

CREATE USER test2 IDENTIFIED BY Test2;
GRANT CONNECT TO test2;

We can see the case sensitive password functionality in operation if we attempt to connect to the new user with both the correct and incorrect case password.

SQL> CONN test2/Test2
Connected.
SQL> CONN test2/test2
ERROR:
ORA-01017: invalid username/password; logon denied

Warning: You are no longer connected to ORACLE.
SQL>

By switching the SEC_CASE_SENSITIVE_LOGON initialization parameter to FALSE we are able to connect using both variations of the password.

CONN / AS SYSDBA
ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = FALSE;

SQL> CONN test2/Test2
Connected.
SQL> CONN test2/test2
Connected.
SQL>

The important thing to remember here is even when case sensitive passwords are not enabled, the original case of the password is retained so it can be used if case sensitivity is subsequently enabled. The following code disables case sensitivity and creates a new user with a mixed case password.

CONN / AS SYSDBA
ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = FALSE;
CREATE USER test3 IDENTIFIED BY Test3;
GRANT CONNECT TO test3;

As you would expect, connection to the user is possible regardless of the case of the password.

SQL> CONN test3/Test3
Connected.
SQL> CONN test3/test3
Connected.
SQL>

If we enable case sensitivity, authentication is done against the mixed case password.

CONN / AS SYSDBA
ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON = TRUE;

SQL> CONN test3/Test3
Connected.
SQL> CONN test3/test3
ERROR:
ORA-01017: invalid username/password; logon denied

Warning: You are no longer connected to ORACLE.
SQL>

The DBA_USERS view includes a PASSWORD_VERSIONS column that indicates the database release in which the password was created or last modified.

SQL> SELECT username, password_versions FROM dba_users;

USERNAME                       PASSWORD
------------------------------ --------
TEST                           10G 11G
SPATIAL_WFS_ADMIN_USR          10G 11G
SPATIAL_CSW_ADMIN_USR          10G 11G
APEX_PUBLIC_USER               10G 11G
.
.
.
SYSTEM                         10G 11G
SYS                            10G 11G
MGMT_VIEW                      10G 11G
OUTLN                          10G 11G

32 rows selected.

SQL>

Users imported from a 10g database have a PASSWORD_VERSIONS value of “10G” and maintain case insensitive passwords independent of the SEC_CASE_SENSITIVE_LOGON parameter setting. Their passwords become case sensitive as soon as they are changed, assuming the SEC_CASE_SENSITIVE_LOGON parameter is set to TRUE. The ignorecase parameter of the orapwd utility allows control over case sensitivity of passwords in the password file. The default value is “n”, meaning the passwords are case sensitive. When privileged users (SYSDBA & SYSOPER) are imported from a previous release their passwords are included in the password file. These users will retain case insensitive passwords until the password is modified. To create case insensitive passwords in the password file, recreate the password file using the ignorecase=y option.

$ orapwd file=orapwDB11Gb entries=100 ignorecase=y password=mypassword

The passwords associated with database links are also case sensitive, which presents some issues when connecting between different releases:

  • 11g to 11g: The database link must be created with the password in the correct case to match the remote users password.
  • 11g to Pre-11g: The database link can be created with the password in any case as case is ignored by the remote database.
  • Pre-11g to 11g: The remote user must have its password modified to be totally in upper case, as this is how it will be stored and passed by the Pre-11g database.

For more information see:

Como instalar o Webmin no Debian Squeeze / Wheezy

Webmin is a web-based system configuration tool. With Webmin it’s easy to configure operating system internals, such as users, disk quotas, services or configuration files, as well as modify and control open source apps, such as the Apache HTTP Server, PHP or MySQL.

1. Install required dependencies

apt-get install apt-show-versions libapt-pkg-perl libauthen-pam-perl libio-pty-perl libnet-ssleay-perl


2. Download Webmin (get the latest version here: http://download.webmin.com/devel/deb/ )

webmin_1.783_all.deb

3. Install Webmin

dpkg -i webmin_1.783_all.deb

Webmin is now installed. You can access it on https://yourserver:10000.

 

 

Fontes: http://www.debiantutorials.com/how-to-install-webmin-on-squeezewheezy/

http://www.debianadmin.com/install-webmin-on-debian-7-6-wheezy.html

Como instalar e configurar o ProFTPD no Debian Wheezy e Ubuntu 14.04

This document describes how to install and configure ProFTPD on a Debian Wheezy Server, it will also work on Ubuntu 14.04. ProFTPD is an FTP daemon for unix and unix-like operating systems. ProFTPD is developed, released and distributed under the GNU Public License (GPL), which basically establishes it as free software, meaning that it may be sold, licensed and otherwise manipulated in any way desired as long as full and complete source code either accompanies any ProFTPD packages or is made available by any and all sites that distribute pre-compiled binaries. The software can be modified by anyone at anytime, as long as all derived works also are licensed under the GNU Public License.

This guide will work for both Ubuntu and Debian server.

 

Fontes:

https://www.howtoforge.com/tutorial/proftpd-installation-on-debian-and-ubuntu/

Como instalar um servidor FTP no Linux Debian (vale pro Ubuntu também)

http://www.hardware.com.br/livros/servidores-linux/instalando-servidor-ftp.html

 

Automatizando startup e shutdown do Oracle 11g R2 no CentOS 6

TEXTO DE: http://mytracelog.blogspot.com.br/2011/07/automatizando-startup-e-shutdown-do.html

Automatizar processos manuais e repetitivos é uma forma de maximizar o tempo, tudo que é manual e repetitivo tem uma grande chance de erro humano. Neste artigo será apresentado como automatizar o startup e o shutdown do banco de dados Oracle 11g R2 x86_64 instalado no CentOS 5.6 x86_64. A automatização será feita através de um script bash que tornará todo o processo simples, seguro, além de não necessitar de nenhuma intervenção humana.

A automatização do processo é muito útil em ambientes 24×7 (24 horas por dia e 7 dias por semana). Implementar o startup automático pode evitar que você tenha que ir até a empresa de madrugada para iniciar o banco devido um pico de energia, neste caso, continue dormindo, pois ao reiniciar a máquina, o banco estará de pé novamente. Descanse bem, pois logo de manhã talvez você precise fazer um recovery, ou se tiver sorte, o próprio Oracle vai se recuperar da queda.

O startup automático iniciará os processos na seguinte ordem:

  1. Listener
  2. Oracle Database
  3. Oracle Enterprise Manager

O shutdown automático finalizará os processos na seguinte ordem:

  1. Oracle Enterprise Manager
  2. Listener
  3. Oracle Database


O processo de automatização é relativamente simples, na própria instalação do Oracle é disponibilizado scripts para startup e shutdown, são eles: $ORACLE_HOME/bin/dbstart e$ORACLE_HOME/bin/dbshut. Esses dois scripts trabalham junto com o arquivo /etc/oratab.

O arquivo oratab é responsável por definir quais instâncias serão inicializadas e finalizadas pelos scriptsdbstart e dbshut. O oratab é composto por entradas que seguem o seguinte padrão:

1
$ORACLE_SID:$ORACLE_HOME:<N|Y>

 

A identificação da instância é representada no primeiro campo, o segundo campo é o diretório home do banco e o terceiro defini se será (Y) ou não (N) utilizado nos scripts dbstart e dbshut.

Para automatizar o processo siga os passos:

    1. Editar o arquivo /etc/oratab, definindo Y para as instâncias que serão automatizadas:
1
[oracle@mytracelog ~]$ vi /etc/oratab
      Arquivo

/etc/oratab

      :
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
#
# This file is used by ORACLE utilities.  It is created by root.sh
# and updated by the Database Configuration Assistant when creating
# a database.
# A colon, ':', is used as the field terminator.  A new line terminates
# the entry.  Lines beginning with a pound sign, '#', are comments.
#
# Entries are of the form:
#   $ORACLE_SID:$ORACLE_HOME:<N|Y>:
#
# The first and second fields are the system identifier and home
# directory of the database respectively.  The third filed indicates
# to the dbstart utility that the database should , "Y", or should not,
# "N", be brought up at system boot time.
#
# Multiple entries with the same $ORACLE_SID are not allowed.
#
#
mytracelog:/u01/app/oracle/product/11.2.0/db_1:Y
    1. Criar o script /etc/init.d/dbora:
1
[root@mytracelog ~]# vi /etc/init.d/dbora
      Script

/etc/init.d/dbora

      :
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
#!/bin/bash
# script: dbora
# autor: sakamoto
# site: <a class="vglnk" href="http://mytracelog.blogspot.com" rel="nofollow"><span>http</span><span>://</span><span>mytracelog</span><span>.</span><span>blogspot</span><span>.</span><span>com</span></a>
# data: 2011-07-31
# versao: 1.0
# alvo: oracle 11g R2 x86_64 & centos 5.6 x86_64
# chkconfig: 35 99 10
# description: startup/shutdown listener, oracle database and enterprise manager
ORA_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
ORA_OWNER=oracle
start(){
   echo "Starting..."
   su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart $ORA_HOME"
   su - $ORA_OWNER -c "$ORA_HOME/bin/emctl start dbconsole"
   touch /var/lock/subsys/dbora
}
stop(){
   echo "Stopping..."
   su - $ORA_OWNER -c "$ORA_HOME/bin/emctl stop dbconsole"
   su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut $ORA_HOME"
   rm -f /var/lock/subsys/dbora
}
restart(){
   stop
   start
}
usage(){
   echo "usage: $0 {start|stop|restart}"
}
if [ `id -u` -ne 0 ]
then
   echo "Este script deve ser executado como root"
   exit
fi
case $1 in
   'start') start;;
   'stop') stop;;
   'restart') restart;;
   *) usage;;
esac
    1. Defina a permissão para script /etc/init.d/dbora:
1
[root@mytracelog ~]# chmod 755 /etc/init.d/dbora
    1. Registre o serviço:
1
[root@mytracelog ~]# chkconfig --add dbora

Automatização completa com sucesso! Agora ao iniciar a máquina podemos ver o serviço dbora sendo iniciado:
startupdbora.png

Ao desligar ou reiniciar a máquina também podemos ver o serviço dbora sendo finalizado:
shutdowndbora.png

Caso necessite fazer o startup e shutdown de forma manual, utilize o usuário root.

A sintaxe do script dbora é a seguinte:

1
2
[root@mytracelog ~]# /etc/init.d/dbora
usage: /etc/init.d/dbora {start|stop|restart}

Para finalizar, algumas considerações sobre o script /etc/init.d/dbora. Como podemos ver, o script dbora é basicamente uma chamada para os outros dois scripts $ORACLE_HOME/bin/dbstart e$ORACLE_HOME/bin/dbshut com mais alguns recursos. Foi implementado o startup e shutdown do Oracle Enterprise Manager. O script dbora possui três opções: start, stop e restart. O restart nada mais é que a chamada do stop seguido do start.

 

OUTRAS FONTES

https://oracle-base.com/articles/linux/automating-database-startup-and-shutdown-on-linux

 

Como habilitar suporte NTFS no CentOS 6.x

TEXTO DE: http://www.sohailriaz.com/how-to-enable-ntfs-support-in-centos-6-3/

In this how to I will describe how to enable NTFS support in CentOS 6.3. By default CentOS 6.x doesnt comes with NTFS support to mount NTFS partition either on hard disk or usb drives. Fedora provies EPEL repository for Red Hat Enterprise Linux. EPEL (Extra Packages for Enterprise Linux) is a volunteer-based community effort from the Fedora project to create a repository of high-quality add-on packages that complement the Fedora-based Red Hat Enterprise Linux (RHEL) and its compatible spinoffs, such as CentOS and Scientific Linux. NTFS drivers ntfs-3g is available through EPEL repository.

1) Preparation

Enable EPEL repository using following command.

2) Install NTFS Drivers.

The above command will install ntfs-3g package which bring NTFS support to your CentOS 6.3 installation. Just plug in your ntfs usb drives or use mount command to enable ntfs hard drive partitions.c