[SourceMod CS:S] Sourcebans Problem

[Dr. Sheldon Cooper]

Hallo,

ich habe ein Problem mit SourceBans!

Ich habe alle Configs genaustens aufeinander abgestimmt, der MySQL-User hat genügend Rechte etc. nur ich weiß nicht woran es liegt, dass SourceBans mir nicht meine Rechte inGame gibt etc.

Auch wenn ich mir manuell Rechte via. die admins.cfg gebe und mich banne, wird mein Ban nicht auf der Website geloggt!

Kann mir jemand helfen?

[Autrux]

Ja, ich kann dir morgen helfen . Bzw, heute.

[UGProjekt]

Ich könnte Ihnen eventuell helfen.
Dafür bräuchte ich jedoch noch ein paar mehr Informationen.
Am besten Sie schicken mir mal eine PN mit einer Kontaktmöglichkeit, wie z.B. Skype oder Steam.

M.f.G

UGProjekt

[Dr. Sheldon Cooper]

@UGProjekt, habe dir eine PN mit meinem Skypenamen zukommenlassen.

[tooti]

Das nächste mal auch bitte den error-log von Sourcemod mit posten, das hilft dann einigen Personen weiter!

[Dr. Sheldon Cooper]

L 04/30/2013 - 13:15:07: [sourcebans.smx] Database failure: [2002]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). See FAQ: http://www.sourcebans.net/node/20
L 04/30/2013 - 13:36:49: [sourcebans.smx] Database failure: [2002]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). See FAQ: http://www.sourcebans.net/node/20
L 04/30/2013 - 14:08:37: [sourcebans.smx] Database failure: [2002]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). See FAQ: http://www.sourcebans.net/node/20
L 04/30/2013 - 14:20:18: [sourcebans.smx] Database failure: [2002]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). See FAQ: http://www.sourcebans.net/node/20
L 04/30/2013 - 14:20:23: [sourcebans.smx] Database failure: [2002]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). See FAQ: http://www.sourcebans.net/node/20
L 04/30/2013 - 14:37:52: [sourcebans.smx] Database failure: [2002]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). See FAQ: http://www.sourcebans.net/node/20
L 04/30/2013 - 15:28:13: [sourcebans.smx] Database failure: [2002]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). See FAQ: http://www.sourcebans.net/node/20
L 04/30/2013 - 16:28:43: [sourcebans.smx] Database failure: [2002]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). See FAQ: http://www.sourcebans.net/node/20
L 04/30/2013 - 16:51:33: [sourcebans.smx] Database failure: [2002]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). See FAQ: http://www.sourcebans.net/node/20
L 04/30/2013 - 17:24:00: [sourcebans.smx] Database failure: [2002]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). See FAQ: http://www.sourcebans.net/node/20
L 04/30/2013 - 17:24:16: [sourcebans.smx] Database failure: [2002]: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2). See FAQ: http://www.sourcebans.net/node/20

[tooti]

Dann ->
Hast du eine externe DB? Wenn ja kommt er nicht drauf

 Spoiler

Your MySQL server does not allow incoming connections from your gameserver. To fix this, you can do either of the following:

* Go into your webserver's control panel and check if there's a section called MySQL Access Hosts or something named similar. There you can add the IP address mentioned in the error. This is usually the IP of your gameserver, but it can also be slightly different, so make sure you copy and paste it exactly from the error.

* The other option is to run the following query on your SourceBans database (for example using phpMyAdmin):
GRANT ALL ON database.* TO 'username'@'ip';

You will have to replace "database" with your SourceBans database name, and "username" and "ip" with those mentioned in the error.

Wenn du noch Hilfe brauchst sag bescheid

[Dr. Sheldon Cooper]

Er konnte nicht auf den MySQL Socket zugreifen.

Habe jetzt meine MySQL-Datei umgeschrieben (die aus dem Verzeichnis '/etc/init.d/').

Diese sieht folgendermaßen aus:

#!/bin/bash
ln -s /var/run/mysqld/mysqld.sock /tmp/mysql.sock
#
### BEGIN INIT INFO
# Provides: mysql
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Should-Start: $network $time
# Should-Stop: $network $time
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start and stop the mysql database server daemon
# Description: Controls the main MySQL database server daemon "mysqld"
# and its wrapper script "mysqld_safe".
### END INIT INFO
#
set -e
set -u
${DEBIAN_SCRIPT_DEBUG:+ set -v -x}

test -x /usr/bin/mysqld_safe || exit 0

. /lib/lsb/init-functions

SELF=$(cd $(dirname $0); pwd -P)/$(basename $0)
CONF=/etc/mysql/my.cnf
MYADMIN="/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf"

# priority can be overriden and "-s" adds output to stderr
ERR_LOGGER="logger -p daemon.err -t /etc/init.d/mysql -i"

# Safeguard (relative paths, core dumps..)
cd /
umask 077

# mysqladmin likes to read /root/.my.cnf. This is usually not what I want
# as many admins e.g. only store a password without a username there and
# so break my scripts.
export HOME=/etc/mysql/

## Fetch a particular option from mysql's invocation.
#
# Usage: void mysqld_get_param option
mysqld_get_param() {
/usr/sbin/mysqld --print-defaults \
| tr " " "\n" \
| grep -- "--$1" \
| tail -n 1 \
| cut -d= -f2
}

## Do some sanity checks before even trying to start mysqld.
sanity_checks() {
# check for config file
if [ ! -r /etc/mysql/my.cnf ]; then
log_warning_msg "$0: WARNING: /etc/mysql/my.cnf cannot be read. See README.Debian.gz"
echo "WARNING: /etc/mysql/my.cnf cannot be read. See README.Debian.gz" | $ERR_LOGGER
fi

# check for diskspace shortage
datadir=`mysqld_get_param datadir`
if LC_ALL=C BLOCKSIZE= df --portability $datadir/. | tail -n 1 | awk '{ exit ($4>4096) }'; then
log_failure_msg "$0: ERROR: The partition with $datadir is too full!"
echo "ERROR: The partition with $datadir is too full!" | $ERR_LOGGER
exit 1
fi
}

## Checks if there is a server running and if so if it is accessible.
#
# check_alive insists on a pingable server
# check_dead also fails if there is a lost mysqld in the process list
#
# Usage: boolean mysqld_status [check_alive|check_dead] [warn|nowarn]
mysqld_status () {
ping_output=`$MYADMIN ping 2>&1`; ping_alive=$(( ! $? ))

ps_alive=0
pidfile=`mysqld_get_param pid-file`
if [ -f "$pidfile" ] && ps `cat $pidfile` >/dev/null 2>&1; then ps_alive=1; fi

if [ "$1" = "check_alive" -a $ping_alive = 1 ] ||
[ "$1" = "check_dead" -a $ping_alive = 0 -a $ps_alive = 0 ]; then
return 0 # EXIT_SUCCESS
else
if [ "$2" = "warn" ]; then
echo -e "$ps_alive processes alive and '$MYADMIN ping' resulted in\n$ping_output\n" | $ERR_LOGGER -p daemon.debug
fi
return 1 # EXIT_FAILURE
fi
}

#
# main()
#

case "${1:-''}" in
'start')
sanity_checks;
# Start daemon
log_daemon_msg "Starting MySQL database server" "mysqld"
if mysqld_status check_alive nowarn; then
log_progress_msg "already running"
log_end_msg 0
else
# Could be removed during boot
test -e /var/run/mysqld || install -m 755 -o mysql -g root -d /var/run/mysqld

# Start MySQL!
/usr/bin/mysqld_safe > /dev/null 2>&1 &

# 6s was reported in #352070 to be too few when using ndbcluster
for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14; do
sleep 1
if mysqld_status check_alive nowarn ; then break; fi
log_progress_msg "."
done
if mysqld_status check_alive warn; then
log_end_msg 0
# Now start mysqlcheck or whatever the admin wants.
output=$(/etc/mysql/debian-start)
[ -n "$output" ] && log_action_msg "$output"
else
log_end_msg 1
log_failure_msg "Please take a look at the syslog"
fi
fi
;;

'stop')
# * As a passwordless mysqladmin (e.g. via ~/.my.cnf) must be possible
# at least for cron, we can rely on it here, too. (although we have
# to specify it explicit as e.g. sudo environments points to the normal
# users home and not /root)
log_daemon_msg "Stopping MySQL database server" "mysqld"
if ! mysqld_status check_dead nowarn; then
set +e
shutdown_out=`$MYADMIN shutdown 2>&1`; r=$?
set -e
if [ "$r" -ne 0 ]; then
log_end_msg 1
[ "$VERBOSE" != "no" ] && log_failure_msg "Error: $shutdown_out"
log_daemon_msg "Killing MySQL database server by signal" "mysqld"
killall -15 mysqld
server_down=
for i in 1 2 3 4 5 6 7 8 9 10; do
sleep 1
if mysqld_status check_dead nowarn; then server_down=1; break; fi
done
if test -z "$server_down"; then killall -9 mysqld; fi
fi
fi

if ! mysqld_status check_dead warn; then
log_end_msg 1
log_failure_msg "Please stop MySQL manually and read /usr/share/doc/mysql-server-5.1/README.Debian.gz!"
exit -1
else
log_end_msg 0
fi
;;

'restart')
set +e; $SELF stop; set -e
$SELF start
;;

'reload'|'force-reload')
log_daemon_msg "Reloading MySQL database server" "mysqld"
$MYADMIN reload
log_end_msg 0
;;

'status')
if mysqld_status check_alive nowarn; then
log_action_msg "$($MYADMIN version)"
else
log_action_msg "MySQL is stopped."
exit 3
fi
;;

*)
echo "Usage: $SELF start|stop|restart|reload|force-reload|status"
exit 1
;;
esac

Grün = Verlinkt die mysql.sock in das Verzeichnis '/tmp/'

[tooti]

Geht es nun? vergesse nicht mysql neu zu starte
Ich sehe (vom sb forum) das es nun geht °^°

[Dr. Sheldon Cooper]

Ja, richtig.

Es funktioniert nun^^ und ja, habe den MySQL-Server neu gestartet