Web Server Error

rubyonrails-talk
1

Starting up the Web Server Error Details:

I executed the following commands:

$ rails new blog

$ cd blog

“Starting up the Web Server”

$ bin/rails server

C:\Ruby200\blog>bin/rails server

‘bin’ is not recognized as an internal or external command,

operable program or batch file.

C:\Ruby200\blog>rails server

Could not find gem ‘tzinfo-data (>= 0) x86-mingw32’ in the gems available on thi

s machine.

Run bundle install to install missing gems.

C:\Ruby200\blog>bundle install

DL is deprecated, please use Fiddle

Fetching gem metadata from https://rubygems.org/……

Resolving dependencies…

Using rake 10.3.2

Using i18n 0.6.11

Gem::InstallError: The ‘json’ native gem requires installed build tools.

Please update your PATH to include build tools or download the DevKit

from ‘http://rubyinstaller.org/downloads’ and follow the instructions

at ‘http://github.com/oneclick/rubyinstaller/wiki/Development-Kit’

An error occurred while installing json (1.8.1), and Bundler cannot continue.

Make sure that gem install json -v '1.8.1' succeeds before bundling.

C:\Ruby200\blog>rails server

Could not find gem ‘tzinfo-data (>= 0) x86-mingw32’ in the gems available on thi

s machine.

Run bundle install to install missing gems.

C:\Ruby200\blog>

Also I could not open the Web Server in http://localhost:3000

Unable to connect

Firefox can’t establish a connection to the server at localhost:3000.

The site could be temporarily unavailable or too busy. Try again in a few

moments.

If you are unable to load any pages, check your computer’s network

connection.

If your computer or network is protected by a firewall or proxy, make sure

that Firefox is permitted to access the Web.

Please help in correcting the problem.

Regards

Rohan Sarker

+913324288069 / +917278539338

www.rohansarker.com

2

I think you may find it difficult to get help when running Rails on Windows. I strongly suggest using a Linux distribution such as Ubuntu, or a Mac as do most developers. You can run Ubuntu in a virtual machine on top of windows (using VirtualBox or VMWare) or you can dual boot your machine to run whichever is appropriate. Once you start using Linux you will wonder why you stuck with Windows. It is great to feel in control of the PC again.

Colin

3

Unfortunately I need to start Web Server in Windows 7. Please let me know if you have any solution for Windows 7.

Regards

Rohan Sarker

+913324288069 / +917278539338

www.rohansarker.com

4

No, I have no solution for that, whether you will find a solution I do not know. Very few Rails servers run on Windows. I suggest that you tell whoever is instructing you that you must do this to think again.

Colin

5

Exactly as the error says, try the following: Please update your PATH to include build tools or download the DevKit

from ‘http://rubyinstaller.org/downloads’ and follow the instructions

at ‘http://github.com/oneclick/rubyinstaller/wiki/Development-Kit’

6

Well if rails and gem are working I wonder:

Have you installed the dev kit?

Looks like the Json gem is failing because the dev kit isnt installed and it needs the build tools inside it

If you have installed the dev kit make sure you follow its instructions. It probably the path issue your error mentions.

Ive used this setup before though so I know its doable

7

Hi Rohan,

To add to Clayton’s message re DevKit. You may use the following instructions.

Download DevKit file from Downloads (DevKit-tdm-32-4.5.2-20110712-1620-sfx.exe)

Extract DevKit to path C:\Ruby200\DevKit

Go to DevKit installation directory, cd C:\Ruby200\DevKit

Run the command ruby dk.rb review

It is useful to review the list of Rubies to be enhanced to use the DevKit and verify the changes you made to it are correct.

Run ruby dk.rb install

  1. Run gem

update --system and run bundle install to your project folder.

Hope everything will go well while fixing these things. :smiley:

Thanks,

Vic

8

I did as mentioned and the command log is as follows:

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Dell>cd C:\Ruby200\DevKit

C:\Ruby200\DevKit>ruby dk.rb review

Unable to find ‘config.yml’. Have you run ‘ruby dk.rb init’ yet?

C:\Ruby200\DevKit>ruby dk.rb

Configures an MSYS/MinGW based Development Kit (DevKit) for

each of the Ruby installations on your Windows system. The

DevKit enables you to build many of the available native

RubyGems that don’t yet have a binary gem.

Usage: ruby dk.rb COMMAND [options]

where COMMAND is one of:

init prepare DevKit for installation

review review DevKit install plan

install install required DevKit executables

and ‘install’ [options] are:

-f, --force overwrite existing helper scripts

C:\Ruby200\DevKit>ruby dk.rb init

[INFO] found RubyInstaller v2.0.0 at C:/Ruby200

Initialization complete! Please review and modify the auto-generated

‘config.yml’ file to ensure it contains the root directories to all

of the installed Rubies you want enhanced by the DevKit.

C:\Ruby200\DevKit>ruby dk.rb install

[INFO] Updating convenience notice gem override for ‘C:/Ruby200’

[INFO] Installing ‘C:/Ruby200/lib/ruby/site_ruby/devkit.rb’

C:\Ruby200\DevKit>gem update --system

Updating rubygems-update

Fetching: rubygems-update-2.4.1.gem (100%)

Successfully installed rubygems-update-2.4.1

Parsing documentation for rubygems-update-2.4.1

Installing ri documentation for rubygems-update-2.4.1

Installing darkfish documentation for rubygems-update-2.4.1

Installing RubyGems 2.4.1

RubyGems 2.4.1 installed

Parsing documentation for rubygems-2.4.1

Installing ri documentation for rubygems-2.4.1

=== 2.4.1 / 2014-07-17

Bug fixes:

  • RubyGems can now be updated on Ruby implementations that do not support

    vendordir in RbConfig::CONFIG. Issue #974 by net1957.

=== 2.4.0 / 2014-07-16

Minor enhancements:

  • The contents command now supports a --show-install-dir option that shows

    only the directory the gem is installed in. Feature request #966 by Akinori

    MUSHA.

  • Added a --build-root option to the install command for packagers. Pull

    request #965 by Marcus Rückert.

  • Added vendor gem support to RubyGems. Package managers may now install gems

    in Gem.vendor_dir with the --vendor option to gem install. Issue #943 by

    Marcus Rückert.

Bug fixes:

  • Kernel#gem now respects the prerelease flag when activating gems.

    Previously this behavior was undefined which could lead to bugs when a

    prerelease version was unintentionally activated. Bug #938 by Joe Ferris.

  • RubyGems now prefers gems from git over installed gems. This allows gems

    from git to override an installed gem with the same name and version. Bug

    #944 by Thomas Kriechbaumer.

  • Fixed handling of git gems in a lockfile with unversioned dependencies. Bug

    #940 by Michael Kaiser-Nyman.

  • The ruby directive in a gem dependencies file is ignored when installing.

    Bug #941 by Michael Kaiser-Nyman.

  • Added open to list of builtin commands (gem open now works). Reported by

    Espen Antonsen.

  • gem open now works with command-line editors. Pull request #962 by Tim

    Pope.

  • gem install -g now respects --conservative. Pull request #950 by Jeremy

    Evans.

  • RubyGems releases announcements now now include checksums. Bug #939 by

    Alexander E. Fischer.

  • RubyGems now expands ~ in $PATH when checking if installed executables will

    be runnable. Pull request #945 by Alex Talker.

  • Fixed gem install -g --explain. Issue #947 by Luis Lavena. Patch by

    Hsing-Hui Hsu.

  • RubyGems locks less during gem activation. Pull request #951 by Aaron

    Patterson and Justin Searls, #969 by Jeremy Tryba.

  • Kernel#gem is now thread-safe. Pull request #967 by Aaron Patterson.

  • RubyGems now handles spaces in directory names for some parts of extension

    building. Pull request #949 by Tristan Hill.

  • RubyGems no longer defines an empty Date class. Pull Request #948 by Benoit

    Daloze.

  • RubyGems respects --document options for gem update again. Bug 946 by

    jonforums. Patch by Hsing-Hui Hsu.

  • RubyGems generates documentation again with --ignore-dependencies. Bug #961

    by Pulfer.

  • RubyGems can install extensions across partitions now. Pull request #970 by

    Michael Scherer.

  • -s is now short for --source which resolves an ambiguity with

    –no-suggestions. Pull request #955 by Alexander Kahn.

  • Added extra test for ~> for 0.0.X versions. Pull request #958 by Mark

    Lorenz.

  • Fixed typo in gem updated help. Pull request #952 by Per Modin.

  • Clarified that the gem description should not be excessively long. Part of

    bug #956 by Renier Morales.

  • Hid documentation of outdated test_files related methods in Specification.

    Guides issue #90 by Emil Soman.

  • RubyGems now falls back to the old index if the rubygems.org API fails

    during gem resolution.

9

I checked with some more options:

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Dell>cd…

C:\Users>cd…

C:>cd Ruby200

C:\Ruby200>cd blog

C:\Ruby200\blog>cd bin

C:\Ruby200\blog\bin>rails server

Could not find gem ‘tzinfo-data (>= 0) x86-mingw32’ in the gems available on thi

s machine.

Run bundle install to install missing gems.

C:\Ruby200\blog\bin>rails

Could not find gem ‘tzinfo-data (>= 0) x86-mingw32’ in the gems available on thi

s machine.

Run bundle install to install missing gems.

C:\Ruby200\blog\bin>

Regards

Rohan Sarker

+913324288069 / +917278539338

www.rohansarker.com

10

For the Development Kit, I could find out only:

DEVELOPMENT KIT

For use with Ruby 1.8.7 and 1.9.3:

For use with Ruby 2.0 (32bits version only):

For use with Ruby 2.0 (x64 – 64bits only)

Regards

Rohan Sarker

+913324288069 / +917278539338

www.rohansarker.com

11

Colin Law writes: > > Unfortunately I need to start Web Server in Windows 7. Please let me know if > > you have any solution for Windows 7. > > No, I have no solution for that, whether you will find a solution I do > not know. Very few Rails servers run on Windows. I suggest that you > tell whoever is instructing you that you must do this to think again.

I've joked with people sometimes that the preferred deployment strategy for Rails on Windows is a VM running Linux, but depending on local politics, it may actually be worth considering. (Running a database this way has significant performance penalties, as the virtualization layer can make a hash of the DB's attempts to optimize physical I/O, but even that may not matter for light or moderate loads.)

rst