Solucionar error no se puede escribir directorio packages

Si te aparece el error ¡Un error ha ocurrido!¡No puedes descargar o instalar nuevos paquetes ya que no se puede escribir en el directorio “Packages”! pero el archivo packages tiene chmod 777, y ellog de errores del foro no te da mayor informacion,no debes buscar mas,este error,si bien no es por chmod no es tan dificl de resolver. lo unico que debes hacer es crear la carpeta temp(con chmod 777)dentro de al carpeta packages.
a mi me paso eso y ¿como di con la solucion? bueno, pues lo que me parecio raro es que si dejaba subir los paquetes,lo verifique en la carpeta packages,pero el problema era al momento de darle al boton instalar,revisando otros foros smf que tengo observe que tienen esa carpeta,que es donde se extraen los archivos cuando pulsamos a ese boton, y bueno lo demas fue probar y ta tan! sirve XD

Configurando el vps

perfomance vps

El caso: Vps con sistema operativo Debian, 2gb de ram y 2 ghz de cpu en leaseweb.El consumo de ram no sube del 50%,pero el uso de cpu sube hasta el 95% con 200 visitas simultaneas en un foro smf.

la bitacora

la posible solucion:instale cacheadores de php y pagespeed, pero no dio ningun resultado,al contrario afecto el uso de recursos,al grado que tenia que reiniciar manualmente el vps cada 12 horas. al final desinstale las extensiones y lo deje todo como al principio.

Vamos de nuevo:ahorita estoy experimentado con cambiar las configuraciones por defecto de apache y mysql,haber como funcionan los cambios

primer cambio apache:

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
StartServers          2
MinSpareServers       3
MaxSpareServers      10
MaxClients          30
MaxRequestsPerChild   1000
</IfModule>

 

Resultados:

No sirvio de nada, agrabao mas el problema :(

Vamos de nuevo…

Segundo cambio:cambiar al configuracion de my.cnf

Se cambio laconfgiuracion del archivo my.cnf,siguiendo las recomendaciones que proponia el script mysqltuner.pl.

Resultados

Ha mejorado el cosnumo de cpu,ahora consume menos del 50%.

nuevo consumo vps leaseweb

dejo la configuracion del my.cnf

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# – “/etc/mysql/my.cnf” to set global options,
# – “~/.my.cnf” to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with –help to get a list of available options and with
# –print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain “#” chars…
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port        = 3306
socket        = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket        = /var/run/mysqld/mysqld.sock
nice        = 0

[mysqld]
local-infile=0
#
# * Basic Settings
#
user        = mysql
pid-file    = /var/run/mysqld/mysqld.pid
socket        = /var/run/mysqld/mysqld.sock
port        = 3306
basedir        = /usr
datadir        = /var/lib/mysql
tmpdir        = /tmp
language    = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
# bind-address        = 127.0.0.1
#
# * Fine Tuning
#
key_buffer        = 16M
max_allowed_packet    = 16M
thread_stack        = 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
#max_connections        = 100
table_cache            = 128
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit    = 1M
query_cache_size        = 32M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log             = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
#log_slow_queries    = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id        = 1
#log_bin            = /var/log/mysql/mysql-bin.log
expire_logs_days    = 10
max_binlog_size         = 100M
#binlog_do_db        = include_database_name
#binlog_ignore_db    = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI “tinyca”.
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem

[mysqldump]
quick
quote-names
max_allowed_packet    = 16M

[mysql]
#no-auto-rehash    # faster start of mysql but no tab completition

[isamchk]
key_buffer        = 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with ‘.cnf’, otherwise they’ll be ignored.
#
!includedir /etc/mysql/conf.d/