Home / user-86487

Jason McCreary's questions

Martin Hope
Jason McCreary
Asked: 2014-06-21 07:10:03 +0800 CST
  • 1

Is there a way to determine the offending file when running https configtest.

For example, instead of:

Warning: DocumentRoot [/var/www/whatever.com/webroot] does not exist
Warning: DocumentRoot [/var/www/example.com/webroot] does not exist

I could see:

Warning: DocumentRoot [/var/www/whatever.com/webroot] does not exist in /etc/httpd/conf.d/file.conf
Warning: DocumentRoot [/var/www/example.com/webroot] does not exist in /etc/httpd/conf.d/other_file.conf

I reviewed help/man and searched, but could not find an option or equivalent command.

apache-2.2
Martin Hope
Jason McCreary
Asked: 2013-03-23 11:26:57 +0800 CST
  • 14

I have looked through the following questions, notably How to use "Instance Store Volumes" storage in Amazon EC2?

However, it didn't answer. I created a EC2 small instance with EBS as the root device. The AWS instance types list an "instance store" of 160GB. But where is it?

$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/xvda1            7.9G  3.6G  4.3G  46% /
tmpfs                 1.9G     0  1.9G   0% /dev/shm

$ mount
/dev/xvda1 on / type ext4 (rw,noatime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

So how to find the empheral store (160GB) and use it.

Note: I am aware of the difference between ephemeral and elastic stores. I need this space for use temporary, transient data used by the application to help with disk I/O between EBS.

UPDATE

Requested output per comments:

$ fdisk -l
Disk /dev/xvda1: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

$ cat /proc/partitions
major minor  #blocks  name

 202        1    8388608 xvda1
amazon-ec2
Martin Hope
Jason McCreary
Asked: 2013-01-08 14:04:27 +0800 CST
  • 2

Currently I cache responses using nginx + fastcgi. I'm in the process of moving my app to AWS. I'm architecting a horizontally scaled approach, but trying to determine where best to put nginx + fastcgi cache.

I found a few solutions from my own research, both with significant drawbacks.

  • Use AWS Elastic Load Balancer to balance a cluster of web apps. Each web app runs it's own nginx and web server stack. Drawback: the cache on each server needs to be warmed. Worst case 1/n the hit rate.
  • Put nginx + fastcgi in front of the AWS ELB so the cache is centralized for maximum hits. Drawback: single point of failure - if nginx dies traffic doesn't pass thru to the ELB. Added nginx instance.

I'd appreciate any suggestions of common architectures that overcome the drawbacks outlined above.

nginx
Martin Hope
Jason McCreary
Asked: 2011-07-04 10:44:21 +0800 CST
  • 1

A few days ago I reset the index (following instructions from help) on a client's Google Mini Appliance after a complete site redesign. Of course at first there were no search results. But at this point the crawl stats seems to be similar to their previous counts. However the search still yields no results.

I have been trying to diagnose the issue. Unfortunately I didn't setup the appliance and am not that familiar with its administration. Any help or suggestions would be appreciated.

I have tried:

  • Restarting the system
  • Switching back to the default collection
  • Switching back to the default front-end

Feel free to take a look at the site: http://floydmemorial.com/

search google gsa