March 9, 2008

Jinzora fiddling

Category: Jinzora — Josh @ 8:19 am

I am twiddling and fiddling with Jinzora again today. I have a new server and am moving everything over to it. During my jinzora installation and setup I noticed that the Metadata retreival was not going to well. I found the site that I has a nice addon for metadata retreival

I used the jz_custom_metadata-1.2.0b1 version on my previous install of Jinzora. It works well.

Note: Ensure that ./jinzora2/services/settings.php is 0777, otherwise you can not update the metadata search settings through the GUI to use the custom metadata search. This is in lieu of setting entire jinzora directory to 0777 as seen here

I also ran into the page caching problem again detailed here. I was frustrated for about an hour until I went back and read my notes.

Notes for installing eaccelerator on Debian:
Ensure that php5-dev and make packages are installed (possibly others I did not need to install anything else)

Execute the following commands
# export PHP_PREFIX=”/usr”
# $PHP_PREFIX/bin/phpize
# ./configure –enable-eaccelerator=shared –with-php-config=$PHP_PREFIX/bin/php-config
# make
# make install
copy eaccelerator.ini from source directory to /etc/php5/conf.d/eaccelerator.ini and modify default value if you need.

eaccelerator.log_file = “/var/log/apache2/eaccelerator_log”

# mkdir /var/cache/eaccelerator
# chmod 0777 /var/cache/eaccelerator
# /etc/init.d/apache2 restart
# ls -al /var/cache/eaccelerator

You should see directories [0-9] and [a-f] in /var/cache/eaccelerator
after browsing around in jinzora execute the following to check if accelerator is creating cache files.

# find /var/cache/eaccelerator -type f -exec ls -l {} \+

additionally (or eventually) you should see information being logged to /var/log/apache2/eaccelerator.log
I have my shared memory size set to 128M so it may just be keeping everything in memory and not pulling it from cache.

August 7, 2007

php5 updated

Category: Jinzora — Josh @ 9:18 pm

I updated debian on my server today. I have done an update for a few months. There was a new PHP5 package that agt-get installed which broke my apache install. I found that eaccelerator needed to be recompiled to make apache work again and to make eaccelerator work with the new version of php5. I ended up downloading the newest version of eaccelerator and recompiling. Jinzora now is running quickly again. during this process I also found that the /tmp/eaccelerator/ directory was missing (this causes eaccelerator to not run), Probably because of a previous update. I have noticed that jinzora has been slow lately. I am suprised that I just noticed that it was not running correctly today. Anyway, everything is back to the way it was before.

April 25, 2007

Jinzora fun

Category: Jinzora — Josh @ 8:43 pm

I discovered this evening that Jinzora is only playing the first few minutes of a song (5 mins?), then going to the next. It can wait until tomorrow.

Metadata problem fixed

Category: Jinzora — Josh @ 8:25 pm

I change upped the memory_limit to 128M in /etc/php5/apache2/php.ini . This has fixed it so that I can run the metadata script from a web browser. I was suprised that I needed to set it this high, but it seems to work ok.

April 24, 2007

Jinzora update

Category: Jinzora — Josh @ 10:16 pm

I changed the memory settings in my /etc/php5/cli/php.ini (upped it to 64m) and was able to execute the metadata script by executing the following command as root. I still can not execute it through the GUI.
>php index.php search_metadata

More Jinzora

Category: Jinzora — Josh @ 9:46 pm

I was having issues with Jinzora not displaying a few buttons on some of the menus. I found that I had to chmod -R 0777 the jinzora directory on my webserver (it was 0755). I hate doing that. BTW the buttons display just fine now. The metadata download still does not work.. it just spins and the page completes loading in about 10 seconds.. whatever script is running in the background is not picking up and actually fetching metadata.

April 22, 2007

code to fix a caching problem

Category: Jinzora — Josh @ 9:06 pm

Well… I did a dist-upgrade on my linux box (was running debian stable 3.1), and upgraded to 4.0. After the upgrade Jinzora would not work. I uninstalled all apache, apache2, php4 and mysql5 packages with the –purge option and reinstalled php5, mysql5, and apache2. I then installed php-dev and compiled/installed eaccelerator to help out my ancient celeron. After I got Jinzora setup I enabled all the previously mentioned tweaks, but started receiving an error after I enabling page caching. I found the following fix on the Jinzora forums posted by
Quasimodo on April 11 2007
In frontend/display.php line 158 change

$signature .= $moreargs[$i];


if(!is_object($moreargs[$i])) {
$signature .= $moreargs[$i];

This code change fixed the caching problem. With the upgrade to php5, mysql5, and all the tweaks, jinzora is night and day…way way way … Way faster on this old celeron. My cross my fingers that the new kernel and modules will play well with my raided /boot and /root partitions.

RE: mysql indexes

Category: Jinzora — Josh @ 2:51 pm

I noticed when I was building indexes for the database that most of these indexes are setup by default now with v 2.7.5 the only index that was not built was the last line of. I tried building the other indexes but I received an error stating something about a duplicate index.
mysql> create index node_art on jz_nodes(main_art);

So I added it

More tweaks

Category: Jinzora — Josh @ 2:48 pm

I also edited the settings.php file in the Jinzora directory and changed the line

$enable_page_caching = “false”;


$enable_page_caching = “true”;

Seems to be a little better now.

Jinzora Tweaks

Category: Jinzora — Josh @ 2:13 pm

I am installing the new version of Jinzora 2.7.5 and decided to tweak the installation to make it run a bit faster on my old celeron 1ghz linux server. I found the following information on the Jinzora forums.

Information on creating mysql indexes to speed up Jinzora.
posted by Ben August 21 2006 – 19:29
# mysql -u[username] -p [database]
— rock out our nodes:
mysql> create index node_level on jz_nodes(level);
mysql> create index node_hidden on jz_nodes(hidden);
mysql> create index node_featured on jz_nodes(featured);
mysql> create index node_leaf on jz_nodes(leaf);
— rock out our tracks:
mysql> create index track_level on jz_tracks(level);
mysql> create index track_hidden on jz_tracks(hidden);
— these are mostly for charts:
mysql> create index node_viewcount on jz_nodes(viewcount desc);
mysql> create index node_dateadded on jz_nodes(date_added desc);
mysql> create index node_dlcount on jz_nodes(dlcount desc);
mysql> create index node_playcount on jz_nodes(playcount desc);
mysql> create index node_lastplayed on jz_nodes(lastplayed desc);
mysql> create index node_rating on jz_nodes(rating_val desc);
— not sure if this does anything:
mysql> create index node_art on jz_nodes(main_art);

I also made the following changes to the mysql configuration file /etc/mysql/my.cnf

# * Fine Tuning
#key_buffer = 16M
#thread_stack = 128K
#thread_cache_size = 80

key_buffer = 64M
max_allowed_packet = 16M
table_cache = 1024
join_buffer_size = 2M
sort_buffer_size = 4M
read_buffer_size = 2M
read_rnd_buffer_size = 768K
myisam_sort_buffer_size = 64M
thread_concurrency = 2

# * Query Cache Configuration
query_cache_limit = 1M
query_cache_size = 32M
query_cache_type = 1

These settings have speed up Jinzora a lot.