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.

I built an AMD FX-9590 System almost 1 year ago, and I had no problems for almost one year.  Then I started having a ton.

Random Restarting

The first issue was that the computer would randomly restart itself.  After going through a ton of debugging steps including reseeding and replacing ram the root cause of this was due to overheating.  I have a corsair water cooling system and dust had built up on the radiator unit and was causing the radiator not to cool down.  The radiator was so hot, one could not touch it with their bare hands.  A can of air and dusting that off, seems to have resolved that issue.

System Instability

About a week or two later after the random restarting, the computer would just lock up.  Sometimes it would lock up 5 minutes after a reboot, other times it would make it a whole 4 or 8 hours.  Even sometimes a full day or two.  I tried a bunch of things, but what really seemed to work was the following.  Please note, I did all these things at once, and since they seemed to work, and I don’t care to play around with the machine anymore, I am keeping all of these things set!  So i don’t know exactly which specific setting or set of settings fixed it.

• AI Tweaker-> AMD Turbo Core – Disable
• Disable Cool N Quiet
• Auto Boost – Off
• C1 and c6 states – disabled
• Installed, and mounted a side case fan, that flows directly onto the northbridge heatsink on the motherboard.

Since I have done the above, the system has been stable, for 4 days now, and has not locked up once.  I am writing these to hopefully help someone else.  Many of these tips I found on tom’s hardware with people having the same issues – so big thanks there!

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!

So we’ve recently worked on converting Debragga.com into a Magento site from a very uncommon platform called vsadmin.  It’s been absolutely stellar.  The design and everything else transferred over, so it was mainly just a back end conversion.  But we’ve seen seo rankings increase, ease of updating products and descriptions, and the availability of all the opportunities that the magento eco system has to offer.

We’ve configured everything as bundled products since everything in the warehouse is a single “part”.  Everything on the site is then broken down into a package containing the sku’s of all the parts that make up the package.  This has helped simplify the pick and pack process tremendously and allowed for quicker training and the allowance of seasonal pickers and packers to assist during busy times.

Anyway, if you haven’t had Dry Aged Beef, or Kobe Beef, I definitely suggest you head over to Debragga and get some!  Your mouth will thank you.

WHen greeted by the error message:

Attribute 'setup_version' is missing for module


This is because the attribute schema_version has changed to setup_version at some point in the M2 development cycle.

Should now be:

I’m creating the test module form the Magento 2 Development Fundamentals course from Magento and ran accross the below error:

Recoverable Error: Argument 1 passed to Training\Test\Controller\Action\Config::__construct() must be an instance of Magento\Framework\App\Action\Context

I found out that the example they gave, they omitted the constructor in the Config.php controller. So let’s add that in:


public function __construct(
\Magento\Framework\App\Action\Context $context,
\Magento\Framework\View\Result\PageFactory $resultPageFactory
) {
$this->resultPageFactory = $resultPageFactory;
parent::__construct($context);
}


Then lastly, since I already tried to run it, I had to clear out some of my var folders and then recompile:


[bessig@dev htdocs]$ sudo rm -Rf var/generation/*
[bessig@dev htdocs]$ sudo rm -Rf var/di
[bessig@dev htdocs]$ sudo rm -Rf var/cache/*
[bessig@dev htdocs]$ sudo rm -Rf var/page_cache/*
[bessig@dev htdocs]$ bin/magento setup:di:compile


Hopefully this helps someone.

Also they did not supply a routes.xml The one I used is as follows:

The page you will call using this route will be: /testing/action/config

Hopefully this saves someone some time! Let me know if your one of the people it helped!

So we use check_mk pretty extensively for all of our servers for health monitoring. Today we added a brand new bare metal centos 7 minimal install on-sit test server to nagios.

We were getting this strange service when we added the box to be invetnoried:

Resolve_mathias-kettner.de
CRITICAL 06-29-2015 13:43:49 3d 5h 14m 51s 3/3 CRIT - mathias-kettner.de could not be resolved

I couldn’t figure out what this check does so I took a peak at the git repo, and saw that its doing a nslooup.  Well my box didn’t have nslookup installed, so a quick

sudo yum install bind-utils -y

seem to do the trick!

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