Technology Blog

I much like many people over the authorize.net forums was receiving this error. Authorize.net seems to be clueless on what this error is or what it even does. Their official documentation even skips over this error message, not even mentioning it.

The problem is that the Accept.js library will catch ANY js error and throw its own handler which will give out this code. What does that mean? It means that even thought Auth.net is telling you there’s an error with thier response, its most likely a JS error on your page.

For example, in my case I had something like this:


input type="input" id="firstName"
...
$("#first_name").val();


The problem above is that #first_name is undefined because I am using camel case when I define it. So in this case, I had a JS error on my page. Unfortunately Authorize.net’s Accept.js module catches ANY js error and throws this silly error message that makes you scratch your head and think anything from SSL, to the tokens are wrong.

Hopefully this post saves someone time. I know this problem ate about 2-3 hours of my time. Looking at the auth.net forums, it looks like many people have wasted way more time.

We began recently working with a new client called Wicker Warehouse, located in Hackensack, NJ. They’ve been in business since 1978, so they know a thing or two about Wicker Patio Furniture, Outdoor Wicker Dining Sets, and Wicker Chairs. Needless to say I know where I will be buying my outdoor furniture from now. The biggest difference is that this stuff is made of quality. The stuff you see on overstock and amazon for a hundred or two cheaper won’t even make it past 2 years. From a marketing perspective it makes an interesting challenge for us – because most of our clients want repeat business. Unfortunately, the product is just so darn good, the repeat business is many years away, so we have to focus on new customer acquisition always! It’s making for a fun and challenging project for sure.

So today I used a mysql replication check found here:

https://gist.github.com/jleggat/1349602

But I couldn’t get it to work.  I created the /usr/lib/check_mk_agent/local/ folder that all of the documentation says you need to put the script into.  I reinventoried, and did everything.  It wasn’t being found.  Then after an hour of searching I came across this gem:

check_mk_agent | head | grep Local

It told me that my local folder was in a different spot:

[root@web2 check_mk_agent]# check_mk_agent | head | grep Local
LocalDirectory: /usr/share/check-mk-agent/local

I moved the script there and wham!  It worked!

After changing a magento store to run on ssl in development we found ourselves facing redirect issues. This is most likely because of the way we are doing ssl on our local development environment.

In order to fix, add this:
SetEnv HTTPS on
to the bottom of .htaccess Case is sensitive in Magento so make sure on is “on” NOT “On” or ON.

run: svn propedit svn:ignore .

Then paste below.


plesk-stat
.htaccess.sample
.modgit
.modman
downloader
errors
install.php
sitemap.xml
var
media


Delete the last commit

Deleting the last commit is the easiest case. Let’s say we have a remote mathnet with branch master that currently points to commit dd61ab32. We want to remove the top commit. Translated to git terminology, we want to force the master branch of the mathnet remote repository to the parent of dd61ab32:

$ git push mathnet +dd61ab32^:master
Where git interprets x^ as the parent of x and + as a forced non-fastforward push. If you have the master branch checked out locally, you can also do it in two simpler steps: First reset the branch to the parent of the current commit, then force-push it to the remote.

$ git reset HEAD^ --hard
$ git push mathnet -f

Originally taken from Christoph Copied here for reference.

For NYC Web Design check out the link.

varnishlog -c -m ‘ReqStart: xx.xxx.xx.xxx’

CentOS 6.x has changed how the default system maintenance cronjobs are scheduled. These are the cron jobs responsible for things like rotating logs and indexing files on the filesystem. That is routine jobs that are best scheduled to run at off peak times when the server is not busy doing more important things like serving money making websites. So how do you go about changing the timing of cron jobs on CentOS or RHEL 6.x?

Or if you want more fine grained control you could just ditch anacron altogether and use /etc/cron.d/dailyjobs

yum remove cronie-anacron
yum install cronie-noanacron sysstat

If you need to ignore multiple folders in svn an easy way to do it is with:
svn propedit svn:ignore .

If you receive the below message:
None of the environment variables SVN_EDITOR, VISUAL or EDITOR are set

Try this:
vi ~/.bash_profile

and insert this line:

export SVN_EDITOR=vi

Note: This won’t work if the directory is already “in” svn. svn rm –keep-local dirname first.

So I had an odd issue with a dell poweredge 2950 server with 5 hard drives in it. They were Hitachi drives 2TB each. I would format the server and use software raid to create a raid 5. Upon turning off the server and booting back up one of the hard drives would be “removed” from the array.

I later realized a complete off shutdown -h now and a cold start were how to reproduce the issue.

I realized that hitachi had a firmware update for my hard drives since they had an issue in some 3ware controllers. My controller a perc 5i is a dell re-branded LSI controller – so I gave it a shot anyway. After flashing the drives I had the same result. I think you should flash the drives to bring them up to date if you are reading this.

What the actual cause of the issue was; I only plugged in one of the two redundant power supplies for the server. In the past, we ran this server with 2 hard drives and had no issue with it being fully functional running on one of the two PSU’s. So when we un-racked the server and brought it to the office for this rebuild we only plugged in one PSU. After all outlets are valuable! Well I plugged in the second PSU into the other wall jack/strip (a different one – I didn’t even bother trying the same jack/strip) and I have not seen the drive go into a “removed” state yet.

So far I have concluded this was the issue. My conclusion is the fact the issue was consistent before and no longer occurs. The reason behind this I think is that these 2GB drives draw alot of power from the server – the initial boot from a cold state requires that the drives spin up. All 5 drives, all fans, and all cpu’s are drawing much more power than regular at the same time during the boot from a cold start. This must have been draining the 750w power supply with my server and causing the PERC 5i to not see one of the drives or to mark it as removed since it did not gain a response in adequate time.

Well that was a waste of about 16-20 hours of work – no I can begin installing the actual software on this machine knowing my raid will be reliable.