this is for alfresco version 3.4.d
have been getting an error similar to the following after configuring a rule in alfresco for converting documents from MS formats to Open Document formats:
Failed to run Actions due to error: 02050010 Transformer for 'application/msword' source mime type and 'application/pdf' target mime type was not found. Operation can't be performed
since I'm now having to dig for the second time on this, figured I'd write it down.
See the following pages:
http://wiki.alfresco.com/wiki/Setting_up_OpenOffice_for_Alfresco (most details)
http://wiki.alfresco.com/wiki/Repository_Configuration (location of the .properties file)
the long and the short of it is this:
find the location of the "alfresco-global.properties" file
[root@OPS5-Alfresco ~]# locate alfresco-global.properties
/opt/alfresco-3.4.d/tomcat/shared/classes/alfresco-global.properties
if you open this file, look for the following line:
ooo.enabled=false
change to true using your favorite editor (vi, nano, etc)
restart alfresco
service alfresco restart (bounces tomcat and mysql)
to know when the alfresco system is up, use "tail -f /opt/alfresco-3.4.d/tomcat/logs/catalina.<date>.log" and look for the line:
INFO: Server startup in 136056 ms
this will confirm that when alfresco starts, OpenOffice will be started with the service and able to convert documents. Happy uploading!
Monday, February 28, 2011
Sunday, January 23, 2011
Print from Linux to a Windows Shared Printer
setting up a print in cups to connect via samba share (or so I thought):
highly recommend the site openprinting.org, they have a very thorough list of printers, and their known working states
I have a Samsung ML-2010, so the drivers aren't included by default for linux, and wonderful Samsung isn't going to help us out.
Some sites that have helped:
- http://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/driverpackages
- http://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/cupsdocumentation
- http://localhost:631/admin (for those unfamiliar, this is the local web management interface for CUPS)
- http://tldp.org/HOWTO/SMB-HOWTO.html#toc8
well, this battle is finally over. When I started, I had a small Zonet ZPS2102 print server (that I've had for years) and it was currently set up over the network and successfully allowing windows systems (XP and 7) to print to it via a samba share. However, as I've been moving to a truly mixed environment at home, I needed to get my linux systems printing capability. I wanted to do this without changing where the printer was plugged in so I didn't lose printing capability in the process. Basically, add the linux systems without affecting anything else.
After banging my head against the SAMBA/CUPS wall for several hours, I decided to try the LPD/LPR configuration on the print server. This was after I'd visitied several sites, learned more about SAMBA than I was expecting at this point, reworked the /etc/samba/smb.conf file several times, and finally plugged the printer into my computer to see if the drivers were working.
With a successful print from a direct physical connection, I decided to try the LPD/LPR config, and it worked like a charm. I hope this saves you some time, I know I'll certainly remember it. So...
Total time to complete this is about 15 to 20 mins tops. (I'll spare you the extra book I wrote while I was banging my head agianst a wall.)
Setting up a ("non"-) supported printer like the Samsung ML-2010 on linux:
WARNING... if you are on RHEL/CEntOS 5.5, you will only have LSB 3.1 installed (and no way to get to LBS 3.2 without compiling it yourself), so make sure you download the correct splix rpm for RHEL/CEntOS 5.
verify signature
[user@linuxbox Downloads]$ rpm -K splix-1.0.1-3lsb3.1.i486.rpm
splix-1.0.1-3lsb3.1.i486.rpm: sha1 md5 OK
you also need to confirm you have the rest of the tools to make this work:
# yum install foomatic ghostscript
# yum --nogpgcheck localinstall splix-1.0.1-3lsb3.1.i486.rpm
navigate to /opt/splix/ppds/Samsung/ and use gunzip to extract the file you need, the files that are installed with .gz won't work for CUPS:
# cd /opt/splix/ppds/Samsung
# gunzip -d Samsung-ML-2010-splix-en.ppd.gz
on the system you want to install the printer on, go to:
http://localhost:631/admin
Click on Administration tab
Click on Add New Printers
click on Add Printer
under Name: => <Unique_Printer_Name> (PrintServer_Samsung_2010)
click contiue
select "LPD/LPR Host or Printer", click continue
device URI: => lpd://<hostname_or_ip>/<lpd_queue_name>
(in my case, lpd://192.168.x.x/Samsung_2010)
Select "Browse" and browse to /opt/splix/ppds/Samsung/
Select the file you unzipped above, click Open
Click "Add Printer"
Click on the Printers Tab
Assign the printer as the default, and print a test page.
Happy Printing!
Extra points: REMOTE INSTALL
To install this remotely, the only extra step was to log in to the other system via ssh with X11 forwarding enabled (-X), and then running "firefox &" to get the web interface for CUPS. Total time is still the same.
$ ssh -X -l user 192.168.x.x (to log in)
I think it is worth noting that I acheived my goal of getting my linux systems to be able to print, but I did not complete my stated goal when I started, which was to set up the printer via SAMBA/CUPS. However, this works just as well for me.
Take-away lesson: if there's another configuration possibility that you haven't tried and you're having to dig deep to solve what you're on, try the other route first.
highly recommend the site openprinting.org, they have a very thorough list of printers, and their known working states
I have a Samsung ML-2010, so the drivers aren't included by default for linux, and wonderful Samsung isn't going to help us out.
Some sites that have helped:
- http://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/driverpackages
- http://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/cupsdocumentation
- http://localhost:631/admin (for those unfamiliar, this is the local web management interface for CUPS)
- http://tldp.org/HOWTO/SMB-HOWTO.html#toc8
well, this battle is finally over. When I started, I had a small Zonet ZPS2102 print server (that I've had for years) and it was currently set up over the network and successfully allowing windows systems (XP and 7) to print to it via a samba share. However, as I've been moving to a truly mixed environment at home, I needed to get my linux systems printing capability. I wanted to do this without changing where the printer was plugged in so I didn't lose printing capability in the process. Basically, add the linux systems without affecting anything else.
After banging my head against the SAMBA/CUPS wall for several hours, I decided to try the LPD/LPR configuration on the print server. This was after I'd visitied several sites, learned more about SAMBA than I was expecting at this point, reworked the /etc/samba/smb.conf file several times, and finally plugged the printer into my computer to see if the drivers were working.
With a successful print from a direct physical connection, I decided to try the LPD/LPR config, and it worked like a charm. I hope this saves you some time, I know I'll certainly remember it. So...
Total time to complete this is about 15 to 20 mins tops. (I'll spare you the extra book I wrote while I was banging my head agianst a wall.)
Setting up a ("non"-) supported printer like the Samsung ML-2010 on linux:
WARNING... if you are on RHEL/CEntOS 5.5, you will only have LSB 3.1 installed (and no way to get to LBS 3.2 without compiling it yourself), so make sure you download the correct splix rpm for RHEL/CEntOS 5.
verify signature
[user@linuxbox Downloads]$ rpm -K splix-1.0.1-3lsb3.1.i486.rpm
splix-1.0.1-3lsb3.1.i486.rpm: sha1 md5 OK
you also need to confirm you have the rest of the tools to make this work:
# yum install foomatic ghostscript
# yum --nogpgcheck localinstall splix-1.0.1-3lsb3.1.i486.rpm
navigate to /opt/splix/ppds/Samsung/ and use gunzip to extract the file you need, the files that are installed with .gz won't work for CUPS:
# cd /opt/splix/ppds/Samsung
# gunzip -d Samsung-ML-2010-splix-en.ppd.gz
on the system you want to install the printer on, go to:
http://localhost:631/admin
Click on Administration tab
Click on Add New Printers
click on Add Printer
under Name: => <Unique_Printer_Name> (PrintServer_Samsung_2010)
click contiue
select "LPD/LPR Host or Printer", click continue
device URI: => lpd://<hostname_or_ip>/<lpd_queue_name>
(in my case, lpd://192.168.x.x/Samsung_2010)
Select "Browse" and browse to /opt/splix/ppds/Samsung/
Select the file you unzipped above, click Open
Click "Add Printer"
Click on the Printers Tab
Assign the printer as the default, and print a test page.
Happy Printing!
Extra points: REMOTE INSTALL
To install this remotely, the only extra step was to log in to the other system via ssh with X11 forwarding enabled (-X), and then running "firefox &" to get the web interface for CUPS. Total time is still the same.
$ ssh -X -l user 192.168.x.x (to log in)
I think it is worth noting that I acheived my goal of getting my linux systems to be able to print, but I did not complete my stated goal when I started, which was to set up the printer via SAMBA/CUPS. However, this works just as well for me.
Take-away lesson: if there's another configuration possibility that you haven't tried and you're having to dig deep to solve what you're on, try the other route first.
Monday, December 27, 2010
Fast user switching in Centos Gnome desktop
Several people have posted wonderful blog entries on how to get the user switching option turned on for Gnome desktop so that when you lock the screen, someone else who would use the computer can log in without logging you out.
The blog I followed can be found here. (complete with screen-shots (= )
However, because of the way that the gnome desktop configuration is set up, this only sets this option for the user you were logged in as when you went through this exercise.
Ok, so I was going to give the file to edit, but as I went looking through gconf-editor some more, I noticed the following:
if you run gconf-editor as root, you will be able to set Default and Mandatory Keys that effect all users. Default = users can edit/change these; Mandatory = locked down to sys admin setting. Once you have chosen keys that should be mandatory/default, you then have to open another window to edit them (one for default, one for mandatory), where you can set the values you want. You can find more information about these settings here.
So, to have user_switch_enabled set to true for all users (aka, someone else can log in when you have locked the screen), here's what I did (screen-shots to follow):
1. as root, run: gconf-editor &
2. Expand Apps, click on gnome-screensaver
3. find user_switch_enabled, right-click, choose "Set as mandatory"
4. Ctrl+M
5. expand tree on left, set "user_switch_enabled"
6. close editors
(note: "yum install gconf-editor" if your system complains in step 1 above)
You may have to log out of the user you were on for the changes to take effect. At this point, if the screen is locked by one user, another user is still able to log in and use the system. If the account you're switching to is not currently logged in, you'll get the standard prompt screen. Otherwise, you'll get the prompt from the locked screen. Everything each user was doing will be saved just as they left it.
(After this, I'll be posting more as I dig into GNOME and other desktops. If there is something you'd like to find out about, leave a comment and I'll see what I can do. I hope to expand this to include most major linux releases and desktops, but we'll see.)
The blog I followed can be found here. (complete with screen-shots (= )
However, because of the way that the gnome desktop configuration is set up, this only sets this option for the user you were logged in as when you went through this exercise.
Ok, so I was going to give the file to edit, but as I went looking through gconf-editor some more, I noticed the following:
if you run gconf-editor as root, you will be able to set Default and Mandatory Keys that effect all users. Default = users can edit/change these; Mandatory = locked down to sys admin setting. Once you have chosen keys that should be mandatory/default, you then have to open another window to edit them (one for default, one for mandatory), where you can set the values you want. You can find more information about these settings here.
So, to have user_switch_enabled set to true for all users (aka, someone else can log in when you have locked the screen), here's what I did (screen-shots to follow):
1. as root, run: gconf-editor &
2. Expand Apps, click on gnome-screensaver
3. find user_switch_enabled, right-click, choose "Set as mandatory"
4. Ctrl+M
5. expand tree on left, set "user_switch_enabled"
6. close editors
(note: "yum install gconf-editor" if your system complains in step 1 above)
You may have to log out of the user you were on for the changes to take effect. At this point, if the screen is locked by one user, another user is still able to log in and use the system. If the account you're switching to is not currently logged in, you'll get the standard prompt screen. Otherwise, you'll get the prompt from the locked screen. Everything each user was doing will be saved just as they left it.
(After this, I'll be posting more as I dig into GNOME and other desktops. If there is something you'd like to find out about, leave a comment and I'll see what I can do. I hope to expand this to include most major linux releases and desktops, but we'll see.)
Sunday, December 26, 2010
Setting up Mach build environment
So, clearly taking me a bit longer to get this going than I thought it would. So here's the first tidbit I can give pretty quickly: I'm working on setting up a build environment using mach (stands for Make A CHroot). This is a nifty tool to work in a clean build environment, and can be found here. Basically, it will pull the packages you need to be able to get a clean build for whatever software you're working with. If you are missing a dependancy, it will pull it automagically, if it can be found in the repos. It also allows you to be able to build software for any version that is supported (ls /etc/mach/dists.d/ to get an idea).
Anyway, I'm just going through setting this up again, on a Centos 5 system that I'm planning on using for builds, and wanted to make a few notes, since the documentation still makes you dig a bit:
Steps followed so far:
1. set up yum for epel repo
2. run: yum install mach
3. add build user(s) to the mach group (ie: usermod -G mach <username>)
4. run: mach -r <root> setup build
5. go check irc or something (approx 5 mins)
remember that the root name needs to have an extension after the architechture, since that is what it is looking for in the /etc/mach/dists.d/ config files (separate file for each major os version). For instance, the base centos 5 root that I just created wouldn't work as "centos-5-i386", it had to be "centos-5-i386-os".
Also, something else that should be mentioned is that it doesn't look like this package currently is able to perform builds for ubuntu/debian packages, but it does support apt-get, so maybe a config file could be created?
Anyway, I'm just going through setting this up again, on a Centos 5 system that I'm planning on using for builds, and wanted to make a few notes, since the documentation still makes you dig a bit:
Steps followed so far:
1. set up yum for epel repo
2. run: yum install mach
3. add build user(s) to the mach group (ie: usermod -G mach <username>)
4. run: mach -r <root> setup build
5. go check irc or something (approx 5 mins)
remember that the root name needs to have an extension after the architechture, since that is what it is looking for in the /etc/mach/dists.d/ config files (separate file for each major os version). For instance, the base centos 5 root that I just created wouldn't work as "centos-5-i386", it had to be "centos-5-i386-os".
Also, something else that should be mentioned is that it doesn't look like this package currently is able to perform builds for ubuntu/debian packages, but it does support apt-get, so maybe a config file could be created?
Monday, November 15, 2010
About
Welcome to The Memory Leak.
Over the last 10 years I've worked in many areas of IT, including systems and database administration, software build and deploy systems, QA automation engineer, and software & database developer.
This blog is where I record what I've done, in the hopes that I can remember things that worked, and possibly benefit someone else. Other topics that I want to record may show up on occasion.
You can reach me on www.linkedin.com/in/deweygarwood
Over the last 10 years I've worked in many areas of IT, including systems and database administration, software build and deploy systems, QA automation engineer, and software & database developer.
This blog is where I record what I've done, in the hopes that I can remember things that worked, and possibly benefit someone else. Other topics that I want to record may show up on occasion.
You can reach me on www.linkedin.com/in/deweygarwood
Subscribe to:
Posts (Atom)