25 Şubat 2013 Pazartesi

329. ECCE, xterm and X forwarding: fixing broken "tail -f on output" in ECCE/'untrusted X11 forwarding' error

To contact us Click HERE

The problem
In ECCE when you highlight a running job on a remote server which you've set up with the frontendMachine option (here and here and here) which is a ROCKS 5.4.3/CentOS server and e.g. hit Alt+L or "Run Mgmt"/"Tail -f on Output file" and nothing happens, and when you set ECCE to provide verbose output (add "ECCE_RCOM_LOGMODE true" to ecce/apps/siteconfig/site_runtime) you see the following errors:

X11 connection rejected because of wrong authentication.X connection to localhost:43.0 broken (explicit kill or server shutdown).
and
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
Obviously there are non-ECCE related situation where you may see these errors too. Doesn't matter -- same solution.


The diagnostics
cat /etc/ssh/sshd_config |grep X11
X11Forwarding yesX11DisplayOffset 10
cat /etc/ssh/ssh_config |grep X11|grep -v ^#
ForwardX11 yes
sudo cat /etc/ssh/sshd_config |grep X11|grep -v ^#
X11Forwarding yesX11DisplayOffset 10

So, why localhost:43? And why isn't it working?From my workstation to the cluster which is connected to the net via the front node, and then from the cluster front to the cluster front's local name.

ssh -X server.external.dnsecho $DISPLAY
localhost:42.0
ssh -X server.local.dns
Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
echo $DISPLAY
localhost:44.0
yet
ssh -Y server.local.dns

works fine.

The solution:
Simpler than I thought:
I edited ~/.ssh/config on the server, and did
Host server.local.dnsHostname server.local.dnsUser meForwardX11 yes ForwardX11Trusted yes

And now it works!

Presumably I could've just edited /etc/ssh_config instead, but it's a multi-user cluster and I'm happier to change things on a user-by-user basis.

343. 'track changes' in LaTeX: collaborative writing

To contact us Click HERE
While I find latex superior to word processors in almost every single aspect, there is one thing I have to admit that MS/Libre/Open Office have over LaTeX: track changes. Since LaTeX is nothing but code you can obviously use something like git or svn to manage versions of .tex code. There are some differences though -- e.g. git would show you the diff output, but not necessarily the context of the changes, and I'm having a difficult enough time convincing people to use LaTeX without having to worry about setting up a git server as well (I can obviously cheat around it by running a local git server, downloading their file and push it to my git server etc, but then I would be the only one who'd be able to track the changes. Also, it's not elegant).

I have a student who is currently preparing a thesis, and while I've managed to give most of my feedback via the pdf annotation function in mendeley, it doesn't feel natural when it should be a simple matter of editing the .tex directly (yet in a way that leaves the student in control over whether to accept or reject the changes).

So here's an exploration of three different ways of passing comments and corrections back and forth when using LaTeX.

I'm also not the first one to ask this question. See e.g. http://tex.stackexchange.com/questions/3653/what-is-the-best-way-to-track-changes-with-non-computer-people

1. Make a pdf and annotate it
 This is a simple and straightforward method for passing comments back and forth. It is not a very convenient method for making any substantial changes though. On top of that, linux does not currently have any particularly useful program for annotating pdf files. See here: http://verahill.blogspot.com.au/2013/02/338-annotating-pdfs-in-linux-revisited.html for more information.

Quite apart from the lack of tool, I really want to emphasize that making small annotations is not a replacement for a tool that allows you to really stir up the text.

2. Using git
You can easily set up your own git server and use that for versioning. http://verahill.blogspot.com.au/2013/01/324-setting-up-private-git-server.html

You can see the version differences using a couple of methods, but gitk might be the easiest one. The downside with this is that you lose some of the context of the changes. Also, it shows you the code that was changed, the changes in the final document (e.g. formatting, figures etc.).

Still it's a pretty intuitive and easy way of tracking changes -- and in terms of versioning it is certainly the best solution. You can fork, roll back and generally have a perfect account of how the document has evolved.
git in particular makes it easy to see added code

In terms of small changes like fixing typos it is a lot more subtle though




3. latexdiff
latexdiff is an easy to use tool that's in the debian repos. Simply do
latexdiff version1.tex version2.tex > diff.tex

and then open diff.tex and compile it to see the changes.

Pleasantly suprised




4. Other solutions
there are plenty of solutions for introducing mark-up directly into the tex document, like trackchanges, changes etc. I've used them in the past but it lack elegance when doing heavier collaborative writing.

Thoughts

I can't help but think that the best solution is to combine git with latexdiff -- or even a special fork of git that uses latexdiff.

Googling shows that apparently I"m not the only one who thinks so: http://gitorious.org/git-latexdiff#more as well as http://tex.stackexchange.com/questions/1325/using-latexdiff-with-git
I haven't actually tested any of those methods yet, and it still more or less requires a common git server.

Ektron eWebEditPro5: Run time Error '0'

To contact us Click HERE
Hi Friends,

If you recently moved to any Siebel Maintenance fix packs 8.0.0.6 and above then you might face an annoying issue with Siebel HTML Editor a.k.a Ektron eWebEditPro Editor!

After you apply the fix pack for Siebel Web Server Extension (SWSE), it upgrades the existing eWebEditPro editor from v4 to v5.

After this upgrade a necessary configuration change is not mentioned in the Maintenance Configuration Section, due to which you will notice that any template tried to be opened in the new HTML Editor results into a blank load & if you right click in the editor it results into a error popup window titled eWebEditProLibCtl5 saying, "Run time error '0'"


 In order to resolve this, you will need to edit the webeditorctrl.htm file under /$SIEBEL_SWSE_ROOT/public/enu/webeditor/

Find out the below code:



and replace it with below code:



After you do this, make sure you do a CLEAR CACHE in your browser else it will still show Javascript errors like:


This happens as the old webeditorctrl.htm file is used from browser cache for loading eWebEditPro Editor.
So ensure you do a clear cache without fail!

Hope this helps resolve patching issue.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SWSE, eWebEditPro, Ektron, HTML Editor, Marketing, WYSIWYG HTML Editor, WYSIWYG, etc.Related Posts : Javascript,SBAv8.0Troubleshooting

24 Şubat 2013 Pazar

329. ECCE, xterm and X forwarding: fixing broken "tail -f on output" in ECCE/'untrusted X11 forwarding' error

To contact us Click HERE

The problem
In ECCE when you highlight a running job on a remote server which you've set up with the frontendMachine option (here and here and here) which is a ROCKS 5.4.3/CentOS server and e.g. hit Alt+L or "Run Mgmt"/"Tail -f on Output file" and nothing happens, and when you set ECCE to provide verbose output (add "ECCE_RCOM_LOGMODE true" to ecce/apps/siteconfig/site_runtime) you see the following errors:

X11 connection rejected because of wrong authentication.X connection to localhost:43.0 broken (explicit kill or server shutdown).
and
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
Obviously there are non-ECCE related situation where you may see these errors too. Doesn't matter -- same solution.


The diagnostics
cat /etc/ssh/sshd_config |grep X11
X11Forwarding yesX11DisplayOffset 10
cat /etc/ssh/ssh_config |grep X11|grep -v ^#
ForwardX11 yes
sudo cat /etc/ssh/sshd_config |grep X11|grep -v ^#
X11Forwarding yesX11DisplayOffset 10

So, why localhost:43? And why isn't it working?From my workstation to the cluster which is connected to the net via the front node, and then from the cluster front to the cluster front's local name.

ssh -X server.external.dnsecho $DISPLAY
localhost:42.0
ssh -X server.local.dns
Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
echo $DISPLAY
localhost:44.0
yet
ssh -Y server.local.dns

works fine.

The solution:
Simpler than I thought:
I edited ~/.ssh/config on the server, and did
Host server.local.dnsHostname server.local.dnsUser meForwardX11 yes ForwardX11Trusted yes

And now it works!

Presumably I could've just edited /etc/ssh_config instead, but it's a multi-user cluster and I'm happier to change things on a user-by-user basis.

343. 'track changes' in LaTeX: collaborative writing

To contact us Click HERE
While I find latex superior to word processors in almost every single aspect, there is one thing I have to admit that MS/Libre/Open Office have over LaTeX: track changes. Since LaTeX is nothing but code you can obviously use something like git or svn to manage versions of .tex code. There are some differences though -- e.g. git would show you the diff output, but not necessarily the context of the changes, and I'm having a difficult enough time convincing people to use LaTeX without having to worry about setting up a git server as well (I can obviously cheat around it by running a local git server, downloading their file and push it to my git server etc, but then I would be the only one who'd be able to track the changes. Also, it's not elegant).

I have a student who is currently preparing a thesis, and while I've managed to give most of my feedback via the pdf annotation function in mendeley, it doesn't feel natural when it should be a simple matter of editing the .tex directly (yet in a way that leaves the student in control over whether to accept or reject the changes).

So here's an exploration of three different ways of passing comments and corrections back and forth when using LaTeX.

I'm also not the first one to ask this question. See e.g. http://tex.stackexchange.com/questions/3653/what-is-the-best-way-to-track-changes-with-non-computer-people

1. Make a pdf and annotate it
 This is a simple and straightforward method for passing comments back and forth. It is not a very convenient method for making any substantial changes though. On top of that, linux does not currently have any particularly useful program for annotating pdf files. See here: http://verahill.blogspot.com.au/2013/02/338-annotating-pdfs-in-linux-revisited.html for more information.

Quite apart from the lack of tool, I really want to emphasize that making small annotations is not a replacement for a tool that allows you to really stir up the text.

2. Using git
You can easily set up your own git server and use that for versioning. http://verahill.blogspot.com.au/2013/01/324-setting-up-private-git-server.html

You can see the version differences using a couple of methods, but gitk might be the easiest one. The downside with this is that you lose some of the context of the changes. Also, it shows you the code that was changed, the changes in the final document (e.g. formatting, figures etc.).

Still it's a pretty intuitive and easy way of tracking changes -- and in terms of versioning it is certainly the best solution. You can fork, roll back and generally have a perfect account of how the document has evolved.
git in particular makes it easy to see added code

In terms of small changes like fixing typos it is a lot more subtle though




3. latexdiff
latexdiff is an easy to use tool that's in the debian repos. Simply do
latexdiff version1.tex version2.tex > diff.tex

and then open diff.tex and compile it to see the changes.

Pleasantly suprised




4. Other solutions
there are plenty of solutions for introducing mark-up directly into the tex document, like trackchanges, changes etc. I've used them in the past but it lack elegance when doing heavier collaborative writing.

Thoughts

I can't help but think that the best solution is to combine git with latexdiff -- or even a special fork of git that uses latexdiff.

Googling shows that apparently I"m not the only one who thinks so: http://gitorious.org/git-latexdiff#more as well as http://tex.stackexchange.com/questions/1325/using-latexdiff-with-git
I haven't actually tested any of those methods yet, and it still more or less requires a common git server.

344. Compile a kernel (3.8) without using kpkg

To contact us Click HERE
Note: There is a much better and easier way: http://verahill.blogspot.com.au/2013/02/342-compiling-kernel-38-on-debian.html . What follows is just done for the sake of exploration.

Post begins:
It is incredibly easy to compile your own kernel on Debian using kernel-package. See e.g. http://verahill.blogspot.com.au/2013/02/342-compiling-kernel-38-on-debian.html

In the interest of learning how to compile a kernel in a more generic way which is applicable to non-debian systems (arch, red hat etc.), here's a method which doesn't rely on kpkg (kernel-package).

The downside is that this method does not produce a set of .deb files, and that you can't uninstall it using apt.

I'll be brief since most things are covered e.g. here.  I looked at this post when writing this.

sudo apt-get install build-essential ncurses-binmkdir ~/tmpcd ~/tmpwget http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.8.tar.bz2tar xvf linux-3.8.tar.bz2cd linux-3.8/cat /boot/config-`uname -r`>.configmake oldconfig

Once you're done answering the questions, do
time make -j3

This takes 29 minutes (AMD Athlon II X3).
time make -j3 modules

This takes 4 minutes. Finish by running

sudo make modules_installsudo make headers_install INSTALL_HDR_PATH=/usr/src/linux-3.8.0sudo make install

Note that the default path for the headers is /usr/include, which doesn't play well with most programs that check for the presence of headers before installation, so use INSTALL_HDR_PATH to specify the destination (at least on debian).

make install takes care of initramfs and grub-update as well and generates
/boot/config-3.8.0
/boot/initrd.img-3.8.0
/boot/System.map-3.8.0
/boot/vmlinuz-3.8.0
And that's really it -- compiling a kernel even without kernel-packages is pretty easy. Reboot and everything should be in working order.

Ektron eWebEditPro5: Run time Error '0'

To contact us Click HERE
Hi Friends,

If you recently moved to any Siebel Maintenance fix packs 8.0.0.6 and above then you might face an annoying issue with Siebel HTML Editor a.k.a Ektron eWebEditPro Editor!

After you apply the fix pack for Siebel Web Server Extension (SWSE), it upgrades the existing eWebEditPro editor from v4 to v5.

After this upgrade a necessary configuration change is not mentioned in the Maintenance Configuration Section, due to which you will notice that any template tried to be opened in the new HTML Editor results into a blank load & if you right click in the editor it results into a error popup window titled eWebEditProLibCtl5 saying, "Run time error '0'"


 In order to resolve this, you will need to edit the webeditorctrl.htm file under /$SIEBEL_SWSE_ROOT/public/enu/webeditor/

Find out the below code:



and replace it with below code:



After you do this, make sure you do a CLEAR CACHE in your browser else it will still show Javascript errors like:


This happens as the old webeditorctrl.htm file is used from browser cache for loading eWebEditPro Editor.
So ensure you do a clear cache without fail!

Hope this helps resolve patching issue.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SWSE, eWebEditPro, Ektron, HTML Editor, Marketing, WYSIWYG HTML Editor, WYSIWYG, etc.Related Posts : Javascript,SBAv8.0Troubleshooting

23 Şubat 2013 Cumartesi

Ektron eWebEditPro5: Run time Error '0'

To contact us Click HERE
Hi Friends,

If you recently moved to any Siebel Maintenance fix packs 8.0.0.6 and above then you might face an annoying issue with Siebel HTML Editor a.k.a Ektron eWebEditPro Editor!

After you apply the fix pack for Siebel Web Server Extension (SWSE), it upgrades the existing eWebEditPro editor from v4 to v5.

After this upgrade a necessary configuration change is not mentioned in the Maintenance Configuration Section, due to which you will notice that any template tried to be opened in the new HTML Editor results into a blank load & if you right click in the editor it results into a error popup window titled eWebEditProLibCtl5 saying, "Run time error '0'"


 In order to resolve this, you will need to edit the webeditorctrl.htm file under /$SIEBEL_SWSE_ROOT/public/enu/webeditor/

Find out the below code:



and replace it with below code:



After you do this, make sure you do a CLEAR CACHE in your browser else it will still show Javascript errors like:


This happens as the old webeditorctrl.htm file is used from browser cache for loading eWebEditPro Editor.
So ensure you do a clear cache without fail!

Hope this helps resolve patching issue.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SWSE, eWebEditPro, Ektron, HTML Editor, Marketing, WYSIWYG HTML Editor, WYSIWYG, etc.Related Posts : Javascript,SBAv8.0Troubleshooting

329. ECCE, xterm and X forwarding: fixing broken "tail -f on output" in ECCE/'untrusted X11 forwarding' error

To contact us Click HERE

The problem
In ECCE when you highlight a running job on a remote server which you've set up with the frontendMachine option (here and here and here) which is a ROCKS 5.4.3/CentOS server and e.g. hit Alt+L or "Run Mgmt"/"Tail -f on Output file" and nothing happens, and when you set ECCE to provide verbose output (add "ECCE_RCOM_LOGMODE true" to ecce/apps/siteconfig/site_runtime) you see the following errors:

X11 connection rejected because of wrong authentication.X connection to localhost:43.0 broken (explicit kill or server shutdown).
and
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
Obviously there are non-ECCE related situation where you may see these errors too. Doesn't matter -- same solution.


The diagnostics
cat /etc/ssh/sshd_config |grep X11
X11Forwarding yesX11DisplayOffset 10
cat /etc/ssh/ssh_config |grep X11|grep -v ^#
ForwardX11 yes
sudo cat /etc/ssh/sshd_config |grep X11|grep -v ^#
X11Forwarding yesX11DisplayOffset 10

So, why localhost:43? And why isn't it working?From my workstation to the cluster which is connected to the net via the front node, and then from the cluster front to the cluster front's local name.

ssh -X server.external.dnsecho $DISPLAY
localhost:42.0
ssh -X server.local.dns
Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
echo $DISPLAY
localhost:44.0
yet
ssh -Y server.local.dns

works fine.

The solution:
Simpler than I thought:
I edited ~/.ssh/config on the server, and did
Host server.local.dnsHostname server.local.dnsUser meForwardX11 yes ForwardX11Trusted yes

And now it works!

Presumably I could've just edited /etc/ssh_config instead, but it's a multi-user cluster and I'm happier to change things on a user-by-user basis.

343. 'track changes' in LaTeX: collaborative writing

To contact us Click HERE
While I find latex superior to word processors in almost every single aspect, there is one thing I have to admit that MS/Libre/Open Office have over LaTeX: track changes. Since LaTeX is nothing but code you can obviously use something like git or svn to manage versions of .tex code. There are some differences though -- e.g. git would show you the diff output, but not necessarily the context of the changes, and I'm having a difficult enough time convincing people to use LaTeX without having to worry about setting up a git server as well (I can obviously cheat around it by running a local git server, downloading their file and push it to my git server etc, but then I would be the only one who'd be able to track the changes. Also, it's not elegant).

I have a student who is currently preparing a thesis, and while I've managed to give most of my feedback via the pdf annotation function in mendeley, it doesn't feel natural when it should be a simple matter of editing the .tex directly (yet in a way that leaves the student in control over whether to accept or reject the changes).

So here's an exploration of three different ways of passing comments and corrections back and forth when using LaTeX.

I'm also not the first one to ask this question. See e.g. http://tex.stackexchange.com/questions/3653/what-is-the-best-way-to-track-changes-with-non-computer-people

1. Make a pdf and annotate it
 This is a simple and straightforward method for passing comments back and forth. It is not a very convenient method for making any substantial changes though. On top of that, linux does not currently have any particularly useful program for annotating pdf files. See here: http://verahill.blogspot.com.au/2013/02/338-annotating-pdfs-in-linux-revisited.html for more information.

Quite apart from the lack of tool, I really want to emphasize that making small annotations is not a replacement for a tool that allows you to really stir up the text.

2. Using git
You can easily set up your own git server and use that for versioning. http://verahill.blogspot.com.au/2013/01/324-setting-up-private-git-server.html

You can see the version differences using a couple of methods, but gitk might be the easiest one. The downside with this is that you lose some of the context of the changes. Also, it shows you the code that was changed, the changes in the final document (e.g. formatting, figures etc.).

Still it's a pretty intuitive and easy way of tracking changes -- and in terms of versioning it is certainly the best solution. You can fork, roll back and generally have a perfect account of how the document has evolved.
git in particular makes it easy to see added code

In terms of small changes like fixing typos it is a lot more subtle though




3. latexdiff
latexdiff is an easy to use tool that's in the debian repos. Simply do
latexdiff version1.tex version2.tex > diff.tex

and then open diff.tex and compile it to see the changes.

Pleasantly suprised




4. Other solutions
there are plenty of solutions for introducing mark-up directly into the tex document, like trackchanges, changes etc. I've used them in the past but it lack elegance when doing heavier collaborative writing.

Thoughts

I can't help but think that the best solution is to combine git with latexdiff -- or even a special fork of git that uses latexdiff.

Googling shows that apparently I"m not the only one who thinks so: http://gitorious.org/git-latexdiff#more as well as http://tex.stackexchange.com/questions/1325/using-latexdiff-with-git
I haven't actually tested any of those methods yet, and it still more or less requires a common git server.

22 Şubat 2013 Cuma

329. ECCE, xterm and X forwarding: fixing broken "tail -f on output" in ECCE/'untrusted X11 forwarding' error

To contact us Click HERE

The problem
In ECCE when you highlight a running job on a remote server which you've set up with the frontendMachine option (here and here and here) which is a ROCKS 5.4.3/CentOS server and e.g. hit Alt+L or "Run Mgmt"/"Tail -f on Output file" and nothing happens, and when you set ECCE to provide verbose output (add "ECCE_RCOM_LOGMODE true" to ecce/apps/siteconfig/site_runtime) you see the following errors:

X11 connection rejected because of wrong authentication.X connection to localhost:43.0 broken (explicit kill or server shutdown).
and
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
Obviously there are non-ECCE related situation where you may see these errors too. Doesn't matter -- same solution.


The diagnostics
cat /etc/ssh/sshd_config |grep X11
X11Forwarding yesX11DisplayOffset 10
cat /etc/ssh/ssh_config |grep X11|grep -v ^#
ForwardX11 yes
sudo cat /etc/ssh/sshd_config |grep X11|grep -v ^#
X11Forwarding yesX11DisplayOffset 10

So, why localhost:43? And why isn't it working?From my workstation to the cluster which is connected to the net via the front node, and then from the cluster front to the cluster front's local name.

ssh -X server.external.dnsecho $DISPLAY
localhost:42.0
ssh -X server.local.dns
Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
echo $DISPLAY
localhost:44.0
yet
ssh -Y server.local.dns

works fine.

The solution:
Simpler than I thought:
I edited ~/.ssh/config on the server, and did
Host server.local.dnsHostname server.local.dnsUser meForwardX11 yes ForwardX11Trusted yes

And now it works!

Presumably I could've just edited /etc/ssh_config instead, but it's a multi-user cluster and I'm happier to change things on a user-by-user basis.

Ektron eWebEditPro5: Run time Error '0'

To contact us Click HERE
Hi Friends,

If you recently moved to any Siebel Maintenance fix packs 8.0.0.6 and above then you might face an annoying issue with Siebel HTML Editor a.k.a Ektron eWebEditPro Editor!

After you apply the fix pack for Siebel Web Server Extension (SWSE), it upgrades the existing eWebEditPro editor from v4 to v5.

After this upgrade a necessary configuration change is not mentioned in the Maintenance Configuration Section, due to which you will notice that any template tried to be opened in the new HTML Editor results into a blank load & if you right click in the editor it results into a error popup window titled eWebEditProLibCtl5 saying, "Run time error '0'"


 In order to resolve this, you will need to edit the webeditorctrl.htm file under /$SIEBEL_SWSE_ROOT/public/enu/webeditor/

Find out the below code:



and replace it with below code:



After you do this, make sure you do a CLEAR CACHE in your browser else it will still show Javascript errors like:


This happens as the old webeditorctrl.htm file is used from browser cache for loading eWebEditPro Editor.
So ensure you do a clear cache without fail!

Hope this helps resolve patching issue.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SWSE, eWebEditPro, Ektron, HTML Editor, Marketing, WYSIWYG HTML Editor, WYSIWYG, etc.Related Posts : Javascript,SBAv8.0Troubleshooting

21 Şubat 2013 Perşembe

329. ECCE, xterm and X forwarding: fixing broken "tail -f on output" in ECCE/'untrusted X11 forwarding' error

To contact us Click HERE

The problem
In ECCE when you highlight a running job on a remote server which you've set up with the frontendMachine option (here and here and here) which is a ROCKS 5.4.3/CentOS server and e.g. hit Alt+L or "Run Mgmt"/"Tail -f on Output file" and nothing happens, and when you set ECCE to provide verbose output (add "ECCE_RCOM_LOGMODE true" to ecce/apps/siteconfig/site_runtime) you see the following errors:

X11 connection rejected because of wrong authentication.X connection to localhost:43.0 broken (explicit kill or server shutdown).
and
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
Obviously there are non-ECCE related situation where you may see these errors too. Doesn't matter -- same solution.


The diagnostics
cat /etc/ssh/sshd_config |grep X11
X11Forwarding yesX11DisplayOffset 10
cat /etc/ssh/ssh_config |grep X11|grep -v ^#
ForwardX11 yes
sudo cat /etc/ssh/sshd_config |grep X11|grep -v ^#
X11Forwarding yesX11DisplayOffset 10

So, why localhost:43? And why isn't it working?From my workstation to the cluster which is connected to the net via the front node, and then from the cluster front to the cluster front's local name.

ssh -X server.external.dnsecho $DISPLAY
localhost:42.0
ssh -X server.local.dns
Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
echo $DISPLAY
localhost:44.0
yet
ssh -Y server.local.dns

works fine.

The solution:
Simpler than I thought:
I edited ~/.ssh/config on the server, and did
Host server.local.dnsHostname server.local.dnsUser meForwardX11 yes ForwardX11Trusted yes

And now it works!

Presumably I could've just edited /etc/ssh_config instead, but it's a multi-user cluster and I'm happier to change things on a user-by-user basis.

Ektron eWebEditPro5: Run time Error '0'

To contact us Click HERE
Hi Friends,

If you recently moved to any Siebel Maintenance fix packs 8.0.0.6 and above then you might face an annoying issue with Siebel HTML Editor a.k.a Ektron eWebEditPro Editor!

After you apply the fix pack for Siebel Web Server Extension (SWSE), it upgrades the existing eWebEditPro editor from v4 to v5.

After this upgrade a necessary configuration change is not mentioned in the Maintenance Configuration Section, due to which you will notice that any template tried to be opened in the new HTML Editor results into a blank load & if you right click in the editor it results into a error popup window titled eWebEditProLibCtl5 saying, "Run time error '0'"


 In order to resolve this, you will need to edit the webeditorctrl.htm file under /$SIEBEL_SWSE_ROOT/public/enu/webeditor/

Find out the below code:



and replace it with below code:



After you do this, make sure you do a CLEAR CACHE in your browser else it will still show Javascript errors like:


This happens as the old webeditorctrl.htm file is used from browser cache for loading eWebEditPro Editor.
So ensure you do a clear cache without fail!

Hope this helps resolve patching issue.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SWSE, eWebEditPro, Ektron, HTML Editor, Marketing, WYSIWYG HTML Editor, WYSIWYG, etc.Related Posts : Javascript,SBAv8.0Troubleshooting

20 Şubat 2013 Çarşamba

Ektron eWebEditPro5: Run time Error '0'

To contact us Click HERE
Hi Friends,

If you recently moved to any Siebel Maintenance fix packs 8.0.0.6 and above then you might face an annoying issue with Siebel HTML Editor a.k.a Ektron eWebEditPro Editor!

After you apply the fix pack for Siebel Web Server Extension (SWSE), it upgrades the existing eWebEditPro editor from v4 to v5.

After this upgrade a necessary configuration change is not mentioned in the Maintenance Configuration Section, due to which you will notice that any template tried to be opened in the new HTML Editor results into a blank load & if you right click in the editor it results into a error popup window titled eWebEditProLibCtl5 saying, "Run time error '0'"


 In order to resolve this, you will need to edit the webeditorctrl.htm file under /$SIEBEL_SWSE_ROOT/public/enu/webeditor/

Find out the below code:



and replace it with below code:



After you do this, make sure you do a CLEAR CACHE in your browser else it will still show Javascript errors like:


This happens as the old webeditorctrl.htm file is used from browser cache for loading eWebEditPro Editor.
So ensure you do a clear cache without fail!

Hope this helps resolve patching issue.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SWSE, eWebEditPro, Ektron, HTML Editor, Marketing, WYSIWYG HTML Editor, WYSIWYG, etc.Related Posts : Javascript,SBAv8.0Troubleshooting

329. ECCE, xterm and X forwarding: fixing broken "tail -f on output" in ECCE/'untrusted X11 forwarding' error

To contact us Click HERE

The problem
In ECCE when you highlight a running job on a remote server which you've set up with the frontendMachine option (here and here and here) which is a ROCKS 5.4.3/CentOS server and e.g. hit Alt+L or "Run Mgmt"/"Tail -f on Output file" and nothing happens, and when you set ECCE to provide verbose output (add "ECCE_RCOM_LOGMODE true" to ecce/apps/siteconfig/site_runtime) you see the following errors:

X11 connection rejected because of wrong authentication.X connection to localhost:43.0 broken (explicit kill or server shutdown).
and
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
Obviously there are non-ECCE related situation where you may see these errors too. Doesn't matter -- same solution.


The diagnostics
cat /etc/ssh/sshd_config |grep X11
X11Forwarding yesX11DisplayOffset 10
cat /etc/ssh/ssh_config |grep X11|grep -v ^#
ForwardX11 yes
sudo cat /etc/ssh/sshd_config |grep X11|grep -v ^#
X11Forwarding yesX11DisplayOffset 10

So, why localhost:43? And why isn't it working?From my workstation to the cluster which is connected to the net via the front node, and then from the cluster front to the cluster front's local name.

ssh -X server.external.dnsecho $DISPLAY
localhost:42.0
ssh -X server.local.dns
Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
echo $DISPLAY
localhost:44.0
yet
ssh -Y server.local.dns

works fine.

The solution:
Simpler than I thought:
I edited ~/.ssh/config on the server, and did
Host server.local.dnsHostname server.local.dnsUser meForwardX11 yes ForwardX11Trusted yes

And now it works!

Presumably I could've just edited /etc/ssh_config instead, but it's a multi-user cluster and I'm happier to change things on a user-by-user basis.

342. Compiling Kernel 3.8 on Debian Testing/Wheezy

To contact us Click HERE
Kernel 3.8 is out now. Not much to say -- the compilation works well using the standard method. The compressed kernel is about 81 Mb to download.
NOTE: kernel 3.8 -- in contrast to the 3.7 series -- now compiles fine on AMD FX 8150 (still testing).
sudo apt-get install kernel-package fakeroot build-essential ncurses-bin ncurses-devmkdir ~/tmpcd ~/tmpwget http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.8.tar.bz2tar xvf linux-3.8.tar.bz2cd linux-3.8/cat /boot/config-`uname -r`>.configmake oldconfig

You will be asked a lot of questions -- how many depends on what version you upgrade from. If in doubt, pick the default answer (i.e. hit enter). If really in doubt, use google.

Then continue:
make-kpkg clean

Do
make menuconfig

if you want to make any specific changes to the kernel (e.g. add support for certain devices)

Then continue:
time fakeroot make-kpkg -j4 --initrd kernel_image kernel_headers

As usual 4 is the number of threads you wish to launch -- make it equal to the number of cores that you have for optimum performance during compilation (more about that here).

The build takes around 20 minutes on a four-core intel i5-2400 with -j4, and 14 minutes on an fx-8150 with -j8 (96 minutes with -j1).

Install:
sudo dpkg -i ../linux-image-3.8.0_3.8.0-10.00.Custom_amd64.deb ../linux-headers-3.8.0_3.8.0-10.00.Custom_amd64.deb

New stuff:


Offload RCU callback processing from boot-selected CPUs (RCU_NOCB_CPU) [N/y/?] (NEW) *Memory placement aware NUMA scheduler (NUMA_BALANCING) [N/y/?] (NEW) *Enable to assign a node which has only movable memory (MOVABLE_NODE) [N/y/?] (NEW)Allow for memory hot-add (MEMORY_HOTPLUG) [Y/n] yAllow for balloon memory compaction/migration (BALLOON_COMPACTION) [Y/n/?] (NEW)Set default setting of cpu0_hotpluggable (BOOTPARAM_HOTPLUG_CPU0) [N/y/?] (NEWDebug CPU0 hotplug (DEBUG_HOTPLUG_CPU0) [N/y/?] (NEW)ACPI tables can be passed via uncompressed cpio in initrd (ACPI_INITRD_TABLE_OVERRIDE) [N/y/?] (NEW)Support multiple cpuidle drivers (CPU_IDLE_MULTIPLE_DRIVERS) [N/y/?] (NEW)"NOTRACK" target support (DEPRECATED) (NETFILTER_XT_TARGET_NOTRACK) [N/m] (NEWDefault SCTP cookie HMAC encoding  > 1. Enable optional MD5 hmac cookie generation (SCTP_DEFAULT_COOKIE_HMAC_MD5) (NEW)    2. Enable optional SHA1 hmac cookie generation (SCTP_DEFAULT_COOKIE_HMAC_SHA1) (NEW)    3. Use no hmac alg in SCTP cookie generation (SCTP_DEFAULT_COOKIE_HMAC_NONE) (NEW)  choice[1-3?]:   Enable optional MD5 hmac cookie generation (SCTP_COOKIE_HMAC_MD5) [Y/?] (NEW) yEnable optional SHA1 hmac cookie generation (SCTP_COOKIE_HMAC_SHA1) [N/y/?] (NEW) *Enable optional MD5 hmac cookie generation (SCTP_COOKIE_HMAC_MD5) [Y/?] (NEW) yDistributed ARP Table (BATMAN_ADV_DAT) [N/y/?] (NEW)Kvaser CAN/USB interface (CAN_KVASER_USB) [N/m/?] (NEW)LSI MPT Fusion SAS 3.0 Device Driver (SCSI_MPT3SAS) [N/m/?] (NEW)Chelsio Communications FCoE support (SCSI_CHELSIO_FCOE) [N/m/?] (NEW) *Marvell 88E6060 ethernet switch chip support (NET_DSA_MV88E6060) [N/m/y/?] (NEW)Marvell 88E6085/6095/6095F/6131 ethernet switch chip support (NET_DSA_MV88E6131) [N/m/y/?] (NEW)Marvell 88E6123/6161/6165 ethernet switch chip support (NET_DSA_MV88E6123_61_65) [N/m/y/?] (NEW) *Cadence devices (NET_CADENCE) [Y/n/?] (NEW)AT91RM9200 Ethernet support (ARM_AT91_ETHER) [N/m/y/?] (NEW)Cadence MACB/GEM support (MACB) [N/m/y/?] (NEW)Broadcom devices (NET_VENDOR_BROADCOM) [Y/?] yMarvell MDIO interface support (MVMDIO) [N/m/y/?] (NEW)CDC MBIM support (USB_NET_CDC_MBIM) [N/m/?] (NEW)Atheros Wireless Cards (ATH_CARDS) [N/m/?] (NEW)Atheros AR5523 wireless driver support (AR5523) [N/m/?] (NEW)Wilocity 60g WiFi card wil6210 support (WIL6210) [N/m/?] (NEW) *Realtek RTL8723AE PCIe Wireless Network Adapter (RTL8723AE) [N/m/?] (NEW)ARC UART driver support (SERIAL_ARC) [N/m/y/?] (NEW) *CBUS I2C driver (I2C_CBUS_GPIO) [N/m/?] (NEW)TS-5500 DIO blocks and compatibles (GPIO_TS5500) [N/m/y/?] (NEW) TI BQ2415x battery charger driver (CHARGER_BQ2415X) [N/m/?] (NEW)Board level reset or power off (POWER_RESET) [N/y/?] (NEW) * Default Thermal governor  > 1. step_wise (THERMAL_DEFAULT_GOV_STEP_WISE) (NEW)    2. fair_share (THERMAL_DEFAULT_GOV_FAIR_SHARE) (NEW)    3. user_space (THERMAL_DEFAULT_GOV_USER_SPACE) (NEW)  choice[1-3?]:   Fair-share thermal governor (FAIR_SHARE) [N/y/?] (NEW)Step_wise thermal governor (STEP_WISE) [Y/?] (NEW) yUser_space thermal governor (USER_SPACE) [N/y/?] (NEW)SSB GPIO driver (SSB_DRIVER_GPIO) [N/y/?] (NEW) *BCMA GPIO driver (BCMA_DRIVER_GPIO) [N/y/?] (NEW)Support for Realtek PCI-E card reader (MFD_RTSX_PCI) [N/m/y/?] (NEW)TI ADC / Touch Screen chip support (MFD_TI_AM335X_TSCADC) [N/m/y/?] (NEW)Support for Nano River Technologies Viperboard (MFD_VIPERBOARD) [N/m/?] (NEW)Support for Retu multi-function device (MFD_RETU) [N/m/?] (NEW) *Maxim MAX8973 voltage regulator  (REGULATOR_MAX8973) [N/m/?] (NEW)TI TPS51632 Power Regulator (REGULATOR_TPS51632) [N/m/?] (NEW)Siano SMS1xxx based MDTV receiver (SMS_USB_DRV) [N/m/?] (NEW)Siano SMS1xxx based MDTV via SDIO interface (SMS_SDIO_DRV) [N/m/?] (NEW)   *Stanton Control System 1 MIDI (SND_SCS1X) [N/m/?] (NEW) *ION iCade arcade controller (HID_ICADE) [N/m/?] (NEW)HID over I2C transport layer (I2C_HID) [N/m/?] (NEW) *Renesas R-Car USB phy support (USB_RCAR_PHY) [N/m/?] (NEW)   *SDHCI support for ACPI enumerated SDHCI controllers (MMC_SDHCI_ACPI) [N/m/?] (NEW)NXP PCF8523 (RTC_DRV_PCF8523) [N/m/?] (NEW)Philips PCF8563/Epson RTC8564 (RTC_DRV_PCF8563) [M/n/?] mUserspace platform driver with generic irq and dynamic memory (UIO_DMEM_GENIRQ) [N/m/?] (NEW)Microsoft Hyper-V Balloon driver (HYPERV_BALLOON) [N/m/?] (NEW) *SystemBase PCI Multiport UART (SB105X) [N/m/y/?] (NEW)TTY over Firewire (FIREWIRE_SERIAL) [N/m/?] (NEW) *F2FS filesystem support (EXPERIMENTAL) (F2FS_FS) [N/m/y/?] (NEW) *Enable CIFS debugging routines (CIFS_DEBUG) [Y/n/?] (NEW)Simplified Mandatory Access Control Kernel Support (SECURITY_SMACK) [N/y/?] (NEW)Camellia cipher algorithm (x86_64/AES-NI/AVX) (CRYPTO_CAMELLIA_AESNI_AVX_X86_64) [N/m/y/?] (NEW)

19 Şubat 2013 Salı

329. ECCE, xterm and X forwarding: fixing broken "tail -f on output" in ECCE/'untrusted X11 forwarding' error

To contact us Click HERE

The problem
In ECCE when you highlight a running job on a remote server which you've set up with the frontendMachine option (here and here and here) which is a ROCKS 5.4.3/CentOS server and e.g. hit Alt+L or "Run Mgmt"/"Tail -f on Output file" and nothing happens, and when you set ECCE to provide verbose output (add "ECCE_RCOM_LOGMODE true" to ecce/apps/siteconfig/site_runtime) you see the following errors:

X11 connection rejected because of wrong authentication.X connection to localhost:43.0 broken (explicit kill or server shutdown).
and
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
Obviously there are non-ECCE related situation where you may see these errors too. Doesn't matter -- same solution.


The diagnostics
cat /etc/ssh/sshd_config |grep X11
X11Forwarding yesX11DisplayOffset 10
cat /etc/ssh/ssh_config |grep X11|grep -v ^#
ForwardX11 yes
sudo cat /etc/ssh/sshd_config |grep X11|grep -v ^#
X11Forwarding yesX11DisplayOffset 10

So, why localhost:43? And why isn't it working?From my workstation to the cluster which is connected to the net via the front node, and then from the cluster front to the cluster front's local name.

ssh -X server.external.dnsecho $DISPLAY
localhost:42.0
ssh -X server.local.dns
Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
echo $DISPLAY
localhost:44.0
yet
ssh -Y server.local.dns

works fine.

The solution:
Simpler than I thought:
I edited ~/.ssh/config on the server, and did
Host server.local.dnsHostname server.local.dnsUser meForwardX11 yes ForwardX11Trusted yes

And now it works!

Presumably I could've just edited /etc/ssh_config instead, but it's a multi-user cluster and I'm happier to change things on a user-by-user basis.

341. Upgrading/installing BankID on 64 bit linux

To contact us Click HERE
There are a few ways to get around the rotten behaviour of bankid. This is one of them:

0. Things to install:
sudo apt-get install iceweasel nspluginwrapper ia32-libs

1. Download BankID and uninstall any previous installations
cd ~/Downloadsmkdir bankidcd bankidwget https://install.bankid.com/Download?defaultFileId=Linux -O bankid.tar.gztar xvf bankid.tar.gzcd BISP-4.19.1.11663/sudo sh install.4.19.1.11663.sh u

2. If you're upgrading, make sure to remove any previous libplugins.so
sudo updatedb && locate libplugins.so
/home/me/Downloads/bankid/BISP-4.19.1.11663/libplugins.so/usr/lib/mozilla/plugins/libplugins.so/usr/lib/mozilla/plugins/npwrapper.libplugins.so/usr/lib/nspluginwrapper/plugins/npwrapper.libplugins.so
sudo nspluginwrapper -r /usr/lib/mozilla/plugins/npwrapper.libplugins.sosudo rm /usr/lib/mozilla/plugins/libplugins.sosudo rm /usr/lib/nspluginwrapper/plugins/npwrapper.libplugins.so

3. Install the new version
sudo sh install.4.19.1.11663.sh i
Installing BankID Security Applicationln: failed to create symbolic link `/usr/lib/firefox-addons/plugins': No such file or directoryWARNING: Failed installing plugin for Firefox 3. Manually add symlink to libplugins.so in your Firefox 3 plugin directory if this browser is to be used.Installation complete.
sudo nspluginwrapper --install /usr/local/lib/personal/libplugins.so

4. Test your installation
Don't bother with test.bankid.com since the idiots won't let you test anything that identifies itself as 64 bit (more about that later). Instead
  • go to http://www.skatteverket.se
  • click on personbevis
  • log in. This should work
5. Testing against test.bankid.com
Everything is in working order but for some idiotic reason bankid.com won't even allow you to test you fancy new 64 bit installation -- and it all boils down the useragent string in iceweasel/firefox identifying itself as running on a 64 bit system (paradoxically, a real 32 bit browser running in a chroot won't work either since the kernel is 64 bit -- in schroot you can use personality=linux32 to get around it, but good luck dealing with the massive memory leaks).

Anyway,
  • open your iceweasel browser
  • type in about:config in the address bar
  • promise that you'll be careful
  • right-click on the page, select New, String
  • In the first box, type general.useragent.override
  • In the second box paste Mozilla/5.0 (X11; Linux i686; rv:10.0.12) Gecko/20100101 Firefox/10.0.12 Iceweasel/10.0.12
You can now go to https://test.bankid.com. I find this a bit humiliating though, and you can use bankid everywhere but bankid.com without having to set the useragent to identify your system as being i686.

Ektron eWebEditPro5: Run time Error '0'

To contact us Click HERE
Hi Friends,

If you recently moved to any Siebel Maintenance fix packs 8.0.0.6 and above then you might face an annoying issue with Siebel HTML Editor a.k.a Ektron eWebEditPro Editor!

After you apply the fix pack for Siebel Web Server Extension (SWSE), it upgrades the existing eWebEditPro editor from v4 to v5.

After this upgrade a necessary configuration change is not mentioned in the Maintenance Configuration Section, due to which you will notice that any template tried to be opened in the new HTML Editor results into a blank load & if you right click in the editor it results into a error popup window titled eWebEditProLibCtl5 saying, "Run time error '0'"


 In order to resolve this, you will need to edit the webeditorctrl.htm file under /$SIEBEL_SWSE_ROOT/public/enu/webeditor/

Find out the below code:



and replace it with below code:



After you do this, make sure you do a CLEAR CACHE in your browser else it will still show Javascript errors like:


This happens as the old webeditorctrl.htm file is used from browser cache for loading eWebEditPro Editor.
So ensure you do a clear cache without fail!

Hope this helps resolve patching issue.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SWSE, eWebEditPro, Ektron, HTML Editor, Marketing, WYSIWYG HTML Editor, WYSIWYG, etc.Related Posts : Javascript,SBAv8.0Troubleshooting

18 Şubat 2013 Pazartesi

329. ECCE, xterm and X forwarding: fixing broken "tail -f on output" in ECCE/'untrusted X11 forwarding' error

To contact us Click HERE

The problem
In ECCE when you highlight a running job on a remote server which you've set up with the frontendMachine option (here and here and here) which is a ROCKS 5.4.3/CentOS server and e.g. hit Alt+L or "Run Mgmt"/"Tail -f on Output file" and nothing happens, and when you set ECCE to provide verbose output (add "ECCE_RCOM_LOGMODE true" to ecce/apps/siteconfig/site_runtime) you see the following errors:

X11 connection rejected because of wrong authentication.X connection to localhost:43.0 broken (explicit kill or server shutdown).
and
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
Obviously there are non-ECCE related situation where you may see these errors too. Doesn't matter -- same solution.


The diagnostics
cat /etc/ssh/sshd_config |grep X11
X11Forwarding yesX11DisplayOffset 10
cat /etc/ssh/ssh_config |grep X11|grep -v ^#
ForwardX11 yes
sudo cat /etc/ssh/sshd_config |grep X11|grep -v ^#
X11Forwarding yesX11DisplayOffset 10

So, why localhost:43? And why isn't it working?From my workstation to the cluster which is connected to the net via the front node, and then from the cluster front to the cluster front's local name.

ssh -X server.external.dnsecho $DISPLAY
localhost:42.0
ssh -X server.local.dns
Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
echo $DISPLAY
localhost:44.0
yet
ssh -Y server.local.dns

works fine.

The solution:
Simpler than I thought:
I edited ~/.ssh/config on the server, and did
Host server.local.dnsHostname server.local.dnsUser meForwardX11 yes ForwardX11Trusted yes

And now it works!

Presumably I could've just edited /etc/ssh_config instead, but it's a multi-user cluster and I'm happier to change things on a user-by-user basis.

340. Issues when compiling Nwchem 6.1.1 -- missing *.fh in src/include

To contact us Click HERE
The problem:
If you modify the nwchem sources, build, do a make realclean and then pack them up to export your patched sources to other nodes you might find that compiling doesn't work that well, yielding errors such as (I'll list them all to help google):

make[1]: *** No rule to make target `/opt/nwchem/nwchem-6.1.1-src_mod/src/include/stdio.fh', needed by `/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libnwcutil.a(basis.o)'.  Stop.make: *** [libraries] Error 1

and
make[1]: *** No rule to make target `/opt/nwchem/nwchem-6.1.1-src_mod/src/include/nwc_const.fh', needed by `/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libnwcutil.a(basis.o)'.  Stop.make: *** [libraries] Error 1nwchem.F:3:0: fatal error: errquit.fh: No such file or directorycompilation terminated.stubs.F:15:0: fatal error: errquit.fh: No such file or directory

and
make[1]: *** No rule to make target `/opt/nwchem/nwchem-6.1.1-src_mod/src/include/errquit.fh', needed by `/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libnwcutil.a(basis.o)'.  Stop.make: *** [libraries] Error 1

and
make[1]: *** No rule to make target `/opt/nwchem/nwchem-6.1.1-src_mod/src/include/util.fh', needed by `/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libnwcutil.a(bas_input.o)'.  Stop.

and
/opt/nwchem/nwchem-6.1.1-src_mod/src/include/util.fh:1:0: fatal error: printlevels.fh: No such file or directorycompilation terminated.make[1]: *** [/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libnwcutil.a(bas_input.o)] Error 1make[1]: *** Waiting for unfinished jobs....

and
basisP.F: In function 'nbf_from_ucont':basisP.F:427:0: warning: '__result_nbf_from_ucont' may be used uninitialized in this function [-Wmaybe-uninitialized]make[2]: warning: -jN forced in submake: disabling jobserver mode.make[1]: warning: -jN forced in submake: disabling jobserver mode.make[1]: *** No rule to make target `/opt/nwchem/nwchem-6.1.1-src_mod/src/include/msgids.fh', needed by `/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libnwcutil.a(geom.o)'.  Stop.

and
make[1]: *** No rule to make target `/opt/nwchem/nwchem-6.1.1-src_mod/src/include/bitops.fh', needed by `/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libnwcutil.a(pstat_alloc.o)'.  Stop.

and
In file included from pstat_alloc.F:12:0:/opt/nwchem/nwchem-6.1.1-src_mod/src/include/bitops.fh:11:0: fatal error: bitops_decls.fh: No such file or directorycompilation terminated.make[1]: *** [/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libnwcutil.a(pstat_alloc.o)] Error 1

and
In file included from pstat_alloc.F:12:0:/opt/nwchem/nwchem-6.1.1-src_mod/src/include/bitops.fh:12:0: fatal error: bitops_funcs.fh: No such file or directorycompilation terminated.make[1]: *** [/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libnwcutil.a(pstat_alloc.o)] Error 1

and
make[2]: warning: -jN forced in submake: disabling jobserver mode.make[2]: *** No rule to make target `/opt/nwchem/nwchem-6.1.1-src_mod/src/include/itri.fh', needed by `/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libnwcutil.a(sym_sh_pair.o)'.  Stop.make[2]: *** Waiting for unfinished jobs....

and
make[2]: *** No rule to make target `/opt/nwchem/nwchem-6.1.1-src_mod/src/include/bgj.fh', needed by `/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libnwints.a(exactd_mem.o)'.  Stop.

and
make[1]: *** No rule to make target `/opt/nwchem/nwchem-6.1.1-src_mod/src/include/numerical_constants.fh', needed by `/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/librimp2.a(rimp2_v_e2.o)'.  Stop.

and
make[2]: *** No rule to make target `/opt/nwchem/nwchem-6.1.1-src_mod/src/include/util_sgroup.fh', needed by `/opt/nwchem/nwchem-6.1.1-src_mod/lib/LINUX64/libdntmc.a(gibbs.o)'.  Stop.

and
nwchem.F:11:0: fatal error: bgj_common.fh: No such file or directory

Solution:
This has been mentioned before on the nwchem forum, but not in explicit enough detail.
The solution is to copy a series of files from src/util and to remove make realclean from your build instructions (or at least do the copying after the make realclean step).

Copy these files
cp src/util/stdio.fh src/include/cp src/util/nwc_const.fh src/include/cp src/util/errquit.fh src/include/cp src/util/util.fh src/include/cp src/util/printlevels.fh src/include/cp src/util/msgids.fh src/include/cp src/util/bitops.fh src/include/cp src/util/bitops_decls.fh src/include/cp src/util/bitops_funcs.fh src/include/cp src/util/itri.fh src/include/cp src/util/bgj.fh src/include/cp src/util/numerical_constants.fh src/include/cp src/util/util_sgroup.fh src/include/cp src/util/bgj_common.fh src/include/

Then build, using e.g.
export LARGE_FILES=TRUEexport TCGRSH=/usr/bin/sshexport NWCHEM_TOP=`pwd`export NWCHEM_TARGET=LINUX64export NWCHEM_MODULES="all python"export PYTHONVERSION=2.7export PYTHONHOME=/usrexport BLASOPT="-L/opt/openblas/lib -lopenblas"export USE_MPI=yexport USE_MPIF=yexport USE_MPIF4=yexport MPI_LOC=/usr/lib/openmpi/libexport MPI_INCLUDE=/usr/lib/openmpi/includeexport LIBRARY_PATH=$LIBRARY_PATH:/usr/lib/openmpi/lib:/opt/openblas/libexport LIBMPI="-lmpi -lopen-rte -lopen-pal -ldl -lmpi_f77 -lpthread"cd $NWCHEM_TOP/srcmake nwchem_configmake FC=gfortran 1>make.log 2>make.errexport FC=gfortrancd ../contrib./getmem.nwchem

Ektron eWebEditPro5: Run time Error '0'

To contact us Click HERE
Hi Friends,

If you recently moved to any Siebel Maintenance fix packs 8.0.0.6 and above then you might face an annoying issue with Siebel HTML Editor a.k.a Ektron eWebEditPro Editor!

After you apply the fix pack for Siebel Web Server Extension (SWSE), it upgrades the existing eWebEditPro editor from v4 to v5.

After this upgrade a necessary configuration change is not mentioned in the Maintenance Configuration Section, due to which you will notice that any template tried to be opened in the new HTML Editor results into a blank load & if you right click in the editor it results into a error popup window titled eWebEditProLibCtl5 saying, "Run time error '0'"


 In order to resolve this, you will need to edit the webeditorctrl.htm file under /$SIEBEL_SWSE_ROOT/public/enu/webeditor/

Find out the below code:



and replace it with below code:



After you do this, make sure you do a CLEAR CACHE in your browser else it will still show Javascript errors like:


This happens as the old webeditorctrl.htm file is used from browser cache for loading eWebEditPro Editor.
So ensure you do a clear cache without fail!

Hope this helps resolve patching issue.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SWSE, eWebEditPro, Ektron, HTML Editor, Marketing, WYSIWYG HTML Editor, WYSIWYG, etc.Related Posts : Javascript,SBAv8.0Troubleshooting

17 Şubat 2013 Pazar

Ektron eWebEditPro5: Run time Error '0'

To contact us Click HERE
Hi Friends,

If you recently moved to any Siebel Maintenance fix packs 8.0.0.6 and above then you might face an annoying issue with Siebel HTML Editor a.k.a Ektron eWebEditPro Editor!

After you apply the fix pack for Siebel Web Server Extension (SWSE), it upgrades the existing eWebEditPro editor from v4 to v5.

After this upgrade a necessary configuration change is not mentioned in the Maintenance Configuration Section, due to which you will notice that any template tried to be opened in the new HTML Editor results into a blank load & if you right click in the editor it results into a error popup window titled eWebEditProLibCtl5 saying, "Run time error '0'"


 In order to resolve this, you will need to edit the webeditorctrl.htm file under /$SIEBEL_SWSE_ROOT/public/enu/webeditor/

Find out the below code:



and replace it with below code:



After you do this, make sure you do a CLEAR CACHE in your browser else it will still show Javascript errors like:


This happens as the old webeditorctrl.htm file is used from browser cache for loading eWebEditPro Editor.
So ensure you do a clear cache without fail!

Hope this helps resolve patching issue.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SWSE, eWebEditPro, Ektron, HTML Editor, Marketing, WYSIWYG HTML Editor, WYSIWYG, etc.Related Posts : Javascript,SBAv8.0Troubleshooting

329. ECCE, xterm and X forwarding: fixing broken "tail -f on output" in ECCE/'untrusted X11 forwarding' error

To contact us Click HERE

The problem
In ECCE when you highlight a running job on a remote server which you've set up with the frontendMachine option (here and here and here) which is a ROCKS 5.4.3/CentOS server and e.g. hit Alt+L or "Run Mgmt"/"Tail -f on Output file" and nothing happens, and when you set ECCE to provide verbose output (add "ECCE_RCOM_LOGMODE true" to ecce/apps/siteconfig/site_runtime) you see the following errors:

X11 connection rejected because of wrong authentication.X connection to localhost:43.0 broken (explicit kill or server shutdown).
and
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
Obviously there are non-ECCE related situation where you may see these errors too. Doesn't matter -- same solution.


The diagnostics
cat /etc/ssh/sshd_config |grep X11
X11Forwarding yesX11DisplayOffset 10
cat /etc/ssh/ssh_config |grep X11|grep -v ^#
ForwardX11 yes
sudo cat /etc/ssh/sshd_config |grep X11|grep -v ^#
X11Forwarding yesX11DisplayOffset 10

So, why localhost:43? And why isn't it working?From my workstation to the cluster which is connected to the net via the front node, and then from the cluster front to the cluster front's local name.

ssh -X server.external.dnsecho $DISPLAY
localhost:42.0
ssh -X server.local.dns
Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
echo $DISPLAY
localhost:44.0
yet
ssh -Y server.local.dns

works fine.

The solution:
Simpler than I thought:
I edited ~/.ssh/config on the server, and did
Host server.local.dnsHostname server.local.dnsUser meForwardX11 yes ForwardX11Trusted yes

And now it works!

Presumably I could've just edited /etc/ssh_config instead, but it's a multi-user cluster and I'm happier to change things on a user-by-user basis.

16 Şubat 2013 Cumartesi

Ektron eWebEditPro5: Run time Error '0'

To contact us Click HERE
Hi Friends,

If you recently moved to any Siebel Maintenance fix packs 8.0.0.6 and above then you might face an annoying issue with Siebel HTML Editor a.k.a Ektron eWebEditPro Editor!

After you apply the fix pack for Siebel Web Server Extension (SWSE), it upgrades the existing eWebEditPro editor from v4 to v5.

After this upgrade a necessary configuration change is not mentioned in the Maintenance Configuration Section, due to which you will notice that any template tried to be opened in the new HTML Editor results into a blank load & if you right click in the editor it results into a error popup window titled eWebEditProLibCtl5 saying, "Run time error '0'"


 In order to resolve this, you will need to edit the webeditorctrl.htm file under /$SIEBEL_SWSE_ROOT/public/enu/webeditor/

Find out the below code:



and replace it with below code:



After you do this, make sure you do a CLEAR CACHE in your browser else it will still show Javascript errors like:


This happens as the old webeditorctrl.htm file is used from browser cache for loading eWebEditPro Editor.
So ensure you do a clear cache without fail!

Hope this helps resolve patching issue.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SWSE, eWebEditPro, Ektron, HTML Editor, Marketing, WYSIWYG HTML Editor, WYSIWYG, etc.Related Posts : Javascript,SBAv8.0Troubleshooting

329. ECCE, xterm and X forwarding: fixing broken "tail -f on output" in ECCE/'untrusted X11 forwarding' error

To contact us Click HERE

The problem
In ECCE when you highlight a running job on a remote server which you've set up with the frontendMachine option (here and here and here) which is a ROCKS 5.4.3/CentOS server and e.g. hit Alt+L or "Run Mgmt"/"Tail -f on Output file" and nothing happens, and when you set ECCE to provide verbose output (add "ECCE_RCOM_LOGMODE true" to ecce/apps/siteconfig/site_runtime) you see the following errors:

X11 connection rejected because of wrong authentication.X connection to localhost:43.0 broken (explicit kill or server shutdown).
and
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
Obviously there are non-ECCE related situation where you may see these errors too. Doesn't matter -- same solution.


The diagnostics
cat /etc/ssh/sshd_config |grep X11
X11Forwarding yesX11DisplayOffset 10
cat /etc/ssh/ssh_config |grep X11|grep -v ^#
ForwardX11 yes
sudo cat /etc/ssh/sshd_config |grep X11|grep -v ^#
X11Forwarding yesX11DisplayOffset 10

So, why localhost:43? And why isn't it working?From my workstation to the cluster which is connected to the net via the front node, and then from the cluster front to the cluster front's local name.

ssh -X server.external.dnsecho $DISPLAY
localhost:42.0
ssh -X server.local.dns
Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
echo $DISPLAY
localhost:44.0
yet
ssh -Y server.local.dns

works fine.

The solution:
Simpler than I thought:
I edited ~/.ssh/config on the server, and did
Host server.local.dnsHostname server.local.dnsUser meForwardX11 yes ForwardX11Trusted yes

And now it works!

Presumably I could've just edited /etc/ssh_config instead, but it's a multi-user cluster and I'm happier to change things on a user-by-user basis.

15 Şubat 2013 Cuma

329. ECCE, xterm and X forwarding: fixing broken "tail -f on output" in ECCE/'untrusted X11 forwarding' error

To contact us Click HERE

The problem
In ECCE when you highlight a running job on a remote server which you've set up with the frontendMachine option (here and here and here) which is a ROCKS 5.4.3/CentOS server and e.g. hit Alt+L or "Run Mgmt"/"Tail -f on Output file" and nothing happens, and when you set ECCE to provide verbose output (add "ECCE_RCOM_LOGMODE true" to ecce/apps/siteconfig/site_runtime) you see the following errors:

X11 connection rejected because of wrong authentication.X connection to localhost:43.0 broken (explicit kill or server shutdown).
and
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
Obviously there are non-ECCE related situation where you may see these errors too. Doesn't matter -- same solution.


The diagnostics
cat /etc/ssh/sshd_config |grep X11
X11Forwarding yesX11DisplayOffset 10
cat /etc/ssh/ssh_config |grep X11|grep -v ^#
ForwardX11 yes
sudo cat /etc/ssh/sshd_config |grep X11|grep -v ^#
X11Forwarding yesX11DisplayOffset 10

So, why localhost:43? And why isn't it working?From my workstation to the cluster which is connected to the net via the front node, and then from the cluster front to the cluster front's local name.

ssh -X server.external.dnsecho $DISPLAY
localhost:42.0
ssh -X server.local.dns
Warning: untrusted X11 forwarding setup failed: xauth key data not generatedWarning: No xauth data; using fake authentication data for X11 forwarding.
echo $DISPLAY
localhost:44.0
yet
ssh -Y server.local.dns

works fine.

The solution:
Simpler than I thought:
I edited ~/.ssh/config on the server, and did
Host server.local.dnsHostname server.local.dnsUser meForwardX11 yes ForwardX11Trusted yes

And now it works!

Presumably I could've just edited /etc/ssh_config instead, but it's a multi-user cluster and I'm happier to change things on a user-by-user basis.

339. Compiling ncdu on ROCKS 5.4.3/Centos 5.6

To contact us Click HERE
du is nice, but ncdu gives a better overview. Nothing odd about building it though:

mkdir ~/tmpcd ~/tmpwget http://dev.yorhel.nl/download/ncdu-1.9.tar.gztar xvf ncdu-1.9.tar.gzcd ncdu-1.9/sudo mkdir /share/apps/tools/ncdu -psudo chown $USER /share/apps/tools/ncdu./configure --prefix=/share/apps/tools/ncdumakemake installecho 'export PATH=$PATH:/share/apps/tools/ncdu/bin' >> ~/.bashrcsource ~/.bashrc

Start by running
ncdu