Forum Activity for @brian

brian
@brian
03/20/18 07:38:59AM
10,157 posts

DB Backups now always stuck in Queue


Using Jamroom

That's because it is exiting before it finishes, so it never makes it to the "clean up" part where it deletes old backups, so you're just increasing in space right now.
brian
@brian
03/20/18 07:38:16AM
10,157 posts

Akismet Question - Probation


Using Jamroom

Correct - it sends any text over for the modified item. Even though in this case he just added an image, the user can actually change other info related to the song, so it has to be checked.

If you can replicate the pending issue let me know and I can check it out.
brian
@brian
03/20/18 07:25:50AM
10,157 posts

Akismet Question - Probation


Using Jamroom

It has nothing to do with the image. When the song is created, all of the text fields (name, etc) are concatenated into a string and submitted to the Akismet spam service.
brian
@brian
03/20/18 07:20:26AM
10,157 posts

DB Backups now always stuck in Queue


Using Jamroom

I can see the queue entry is still in your queue, but the process is no longer running, so something is up. Please open a ticket for me with your admin login so I can check it out.

Thanks!
brian
@brian
03/20/18 07:19:30AM
10,157 posts

Akismet Question - Probation


Using Jamroom

Do you have the Akismet API configured? The only other thing it could be is that Akismet sees the item as being Spam.
brian
@brian
03/19/18 06:32:37PM
10,157 posts

Akismet Question - Probation


Using Jamroom

That doesn't really make sense - the probation check is only on user accounts that are NEWER than config'd:

// Is this user in probation
$old = (time() - (86400 * $_conf['jrAkismet_probation']));
if ($_user['_created'] > $old) {

So only if the user account's _created time is NEWER than the number of probation days do they even go into the check.
brian
@brian
03/19/18 06:30:25PM
10,157 posts

Unable to go to next page


Installation and Configuration

Enable the Beta Channel in ACP -> Marketplace -> Tools -> Marketplace Channels.
brian
@brian
03/19/18 06:29:51PM
10,157 posts

DB Backups now always stuck in Queue


Using Jamroom

Yeah something is up then - if it's dying each night then it's hitting something and breaking. Check in your Activity Log and Error Log for any entries that might give a clue to what's up.
brian
@brian
03/19/18 04:56:29PM
10,157 posts

DB Backups now always stuck in Queue


Using Jamroom

So this can be normal (at least your second screenshot). The DB backup queue automatically sleeps for ~15 minutes (for the daily backup) and 10 minutes for the hourly backup. This is done since the backups tend to be a bit of "heavy hitters" in that they can put a larger load on the system while they are running. So we sleep for a bit so all the other queues that kick off hourly and daily can finish first.

So "sleeping" is totally normal - just let it sleep.

In your first screenshot however, the daily backup that started on the 18th is clearly "hung" - it's been running for 20 hours - and there is now a SECOND backup that is waiting to be worked (for the 19th). So delete the first one - it's not running any more.

Let me know if that helps.
brian
@brian
03/19/18 04:14:51PM
10,157 posts

Jamroom Sites Slow on Dedicated Server


Installation and Configuration

I don't know how much RAM your server has, bit here's a MySQL config for a 8 Gig RAM server that should work no problem with Jamroom:

#
# 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]
#
# * 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
lc-messages-dir	= /usr/share/mysql
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  8 GIG RAM
#
key_buffer              = 256M
max_allowed_packet      = 32M
table_open_cache        = 1536
table_definition_cache  = 1536
open_files_limit        = 10240
tmp_table_size          = 256M
max_heap_table_size     = 256M
sort_buffer_size        = 2M
read_buffer_size        = 2M
read_rnd_buffer_size    = 768K
max_connections         = 200
innodb_buffer_pool_size = 2G
innodb_flush_method     = O_DIRECT
innodb_flush_log_at_trx_commit = 0
ft_min_word_len         = 3
ft_stopword_file        = ""

# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover-options  = BACKUP
#
# * Query Cache Configuration
#
query_cache_limit	    = 1M
query_cache_size        = 160M
#
# * 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 log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Here you can see queries with especially long duration
slow_query_log      = 1
slow_query_log_file = /var/log/mysql/mysql-slow.log
long_query_time     = 3

# 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/

(Note - this is for Ubuntu)
  64